I cleaned up the build process, fixed warnings reported during the build and especially ensured that javadoc-jar and sources-jar artifacts are created during the build. This is a requirement for Maven-Central deployment nowadays (see
https://maven.apache.org/repository/guide-central-repository-upload.html).
With these changes, hopefully you should be able to deploy an updated version to Maven-Central. However, to do so I would recommend to reset the version to 2.34-SNAPSHOT and delete the failed tags args4j-site-2.34 and args4j-site-2.35 before to prevent gaps in the version numbers deployed to Maven-Central.
Hi @kohsuke,
I cleaned up the build process, fixed warnings reported during the build and especially ensured that javadoc-jar and sources-jar artifacts are created during the build. This is a requirement for Maven-Central deployment nowadays (see https://maven.apache.org/repository/guide-central-repository-upload.html).
With these changes, hopefully you should be able to deploy an updated version to Maven-Central. However, to do so I would recommend to reset the version to
2.34-SNAPSHOT
and delete the failed tagsargs4j-site-2.34
andargs4j-site-2.35
before to prevent gaps in the version numbers deployed to Maven-Central.