Incorrect version number parsing with Maven metadata generated by Gradle 8.4
Closed this issue · 0 comments
ethauvin commented
The latest version of Gradle is now generating maven-metadata files with the artifact version tag defined as the last tag.
This causes bld to incorrectly set the artifact version number, as it is currently expecting the version tag to be defined first. Moving the tag back to the top will fix the problem.
The problematic code is here.
The above metadata files are taken from my local repository, but the problem is identical with published artifacts, for example:
net.thauvin.erik:bitly-shorten:1.0.1-SNAPSHOT in SONATYPE_SNAPSHOTS_LEGACY