Open mkarg opened 4 years ago
@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..
<dependency>
<groupId>com.beust</groupId> <!-- WRONG -->
<artifactId>jcommander</artifactId>
<version>[1.82,)</version>
</dependency>
And I was able to pull 1.83 after I switched to this:
<dependency>
<groupId>org.jcommander</groupId> <!-- Correct as of late 2023 -->
<artifactId>jcommander</artifactId>
<version>[1.82,)</version>
</dependency>
Thanks, cheers!
I would be happy if jCommander 1.80 could be pushed to Maven Central. :-)