-
Notifications
You must be signed in to change notification settings - Fork 333
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
Maven Central Updates #499
Comments
@cbeust Please consider this issue. Thanks. :-) |
@cbeust Could you please at least clearly point out that you never will do that, so everybody knows what's the official project policy? Otherwise, I hereby offer that I will frequently upload all new releases on Maven Central in the name of this project, if you agree that I claim your group ID at Sonatype. |
Meanwhile jCommander 1.81 is published on Maven Central. I wonder why not pushing 1.80? |
1.83 is also missing from Maven Central. |
No it is not. You can find it here: https://central.sonatype.com/artifact/org.jcommander/jcommander/1.83. |
Ah, thanks for the link. That gave me the solution.. I had this in my pom..
And I was able to pull 1.83 after I switched to this:
Thanks, cheers! |
I would be happy if jCommander 1.80 could be pushed to Maven Central. :-)
The text was updated successfully, but these errors were encountered: