Publish jna 3.3.0 to maven central ?

[krosenvold]

3.3.0 is not getting pushed to maven central. Maybe consider pusing directly to central via https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide or similar ?

[krosenvold]

I had a little chat with juven over at #maven and he tells me you have published to an old deprecated java.net maven reposistory that will be closed soon (http://download.java.net/maven/2/ ). This does not have automatic synchronization to maven central.

If you can publish to maven.java.net it would be picked up automatically

[juven]

fyi, there's already a jira ticket created for deploying to maven.java.net http://java.net/jira/browse/MAVEN2_REPOSITORY-55

[twall]

I got a note about the deprecation of the java.net repo; I put in a ticket to open an account on whatever they were moving to, but the final instructions for actually moving were over two pages long and looked decidedly non-trivial. Not the kind of thing I'd choose to spend my weekend doing.

Patches to build.xml to push out to the new maven repo are welcome.

[krosenvold]

If you can send me a link or a copy to the instructions you were given I can give you a pull request. I'm afraid a fair bit of the instructions relate to one-time setup of your machine, but I can do the rest ;)

[twall]

See the link juven provided: http://java.net/jira/browse/MAVEN2_REPOSITORY-55

[krosenvold]

Those are the links to deploy, not the instructions as such. I'll just use the standard ant technique if there's no special guides.

[davidhoyt]

Any chance of getting v3.4.0 pushed to maven central?

[twall]

I have no idea what I'm doing with maven (nor likely to have cause to figure it out soon), so someone with more motivation (or less activation energy) than me needs to provide patches to push to either java.net (which will get pushed to central) or maven central proper.

[krosenvold]

Fixed