JReleaser 1.3.1 has been released!

JReleaser v1.3.1 has just been released! This is quick fix release given a pair of issues found with deployment to Maven Central, recently releases in v1.3.0. We decided to cut a quick release now instead of waiting for the next stable release (1.4.0) by the end of December 2022. The full list of issues can be found at the v1.3.1 milestone.

Maven Central

Deployment to Maven Central is performed by the Nexus2 deployer. Operations that modify the state of a remote staged repository (close, drop, release) may take some time depending on the size of the repository. JReleaser v1.3.1 adds an option to wait and retry state transition checks.

Maven Plugin

As it happened, v1.3.0 of the jreleaser-maven-plugin had a transitive dependency on commons-io:2.11.0 that may r may not be fulfilled depending on your local setup, resulting on a build failure when that wasn't the case. JReleaser v1.3.1 fixes this issue by properly configuring plugin dependencies.

Environment Variables

Resolving multiple environment variables associated with a single entry was not working as we expected. This prevented the use of variables such as JRELEASER_NEXUS2_MAVEN_CENTRAL_USERNAME and JRELEASER_NEXUS2_USERNAME from being used to resolve the target username for a Nexus2 deployer named maven-central. This problem has been fixed.

As always, feedback is welcomed, feel free to file a ticket or start a discussion topic.

Keep on coding!

Image by Jiří Rotrekl from Pixabay

Liked it? Take a second to support aalmiray on Patreon!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

ˆ Back To Top