-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish to maven central #4
Comments
Absolutely! I am (very slowly) working through the process now. |
+1 |
2 similar comments
+1 |
+1 |
I opened issue #6 which might help with the process of getting things into Central. |
In the mean time I have pushed a version of this to Maven Central under the following information
This should make it into Central on the next sync from OSSRH, so give it a couple of hours. @damiengiese let me know if you need help with the process for getting this into Central under the official group ID, I've done this for a few other projects and I'm happy to answer any questions. |
+1 |
@cosmin, thanks very much for your help. I've spent quite a lot of time learning about git and PGP in preparation to publish docopt to Maven Central, but I admit I've been hung up on updating the POM. It looks like you've added everything called out in the Maven Central Component Requirements, so that's a big help. I'm still not sure that I understand how to perform a release using Maven, however. The technique you've provided (using the |
@damiengiese the only difference between what they recommend and what I'm doing is that I am using the Maven release plugin rather the Nexus staging plugin. The release plugin takes care of a lot of house keeping for you. When working on a 1.0-SNAPSHOT for example, you would normally have to do the following tasks by hand:
As you can see, this is a lot of work, and in my experience it's pretty hard to not screw this up when doing it by hand. Specifically most people end up tagging before they change the version to the release version and then you end up with a tag that is not what is actually built. Or they forget to bump the version to the next development version, etc. So this is where the Maven release plugin comes in handy. It has two steps.
When you use the release plugin, it sets the property In newer versions of the maven release plugin they added a new configuration section called
Which turns off the If you feel more comfortable with that approach because of the documentation, I can update my pull request. But in either case, I highly recommend using the release plugin rather than doing manual releases. |
+1 |
2 similar comments
+1 |
+1 |
I'd suggest to simply release it to jcenter https://bintray.com/bintray/jcenter instead. There you just need to package it along with the sources using
and you can upload the file via the web-interface. |
please? I'd like to use it but checking jars into git just stinks. |
@fsparv what about the intermediate workaround of using
as documented earlier in this thread? |
There now seem to be several versions published, and some folks appear to have stolen appropriate maven coordinates too... :( https://mvnrepository.com/search?q=docopt |
Docopt.java should be published to the maven central repository for use by other applications.
The text was updated successfully, but these errors were encountered: