[ https://issues.apache.org/jira/browse/MRELEASE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862657#comment-17862657 ]
Basil Crow commented on MRELEASE-1151: -------------------------------------- See https://github.com/jenkinsci/jenkins/commits/master for the details — our 2.465 release failed, while 2.466 succeeded. https://github.com/jenkinsci/jenkins/commit/dd7a6874e6704bb7163a98c728b3b11a78be53f6 failed to update the version, creating a {{jenkins-2.465}} tag whose version was after interpolation (incorrectly) 2.465-SNAPSHOT. I believe this was then rejected by Artifactory in the deployment phase, since snapshots aren't allowed in our release repository. Note that this worked in 3.0.1. After that https://github.com/jenkinsci/jenkins/commit/d0e050b90f6926f2e56d7e634deed2bc57d83d54 set the version after interpolation (incorrectly) to 2.465-SNAPSHOT-SNAPSHOT. You can compare these two commits with the corresponding two commits for 2.466 or 2.464 to see how things are working with 3.0.1. > Maven Release Plugin fails to adjust version (regression in 3.1.0) > ------------------------------------------------------------------ > > Key: MRELEASE-1151 > URL: https://issues.apache.org/jira/browse/MRELEASE-1151 > Project: Maven Release Plugin > Issue Type: Bug > Components: prepare > Affects Versions: 3.1.0 > Environment: Ubuntu 22.04.4 LTS x86_64 > Reporter: Basil Crow > Priority: Blocker > > h3. Steps to reproduce > # Run {{git clone [https://github.com/jenkinsci/text-finder-plugin.git]}} > # Using Java 17 and Maven 3.9.8, run {{mvn release:prepare > -DpushChanges=false}} > h3. Expected results > {panel:title=Note} > These are the _actual_ results with Maven Release Plugin 3.0.1. > {panel} > The {{[maven-release-plugin] prepare release}} commit adjusts > {{<tag>${scmTag}</tag>}} to e.g. {{<tag>text-finder-1.29</tag>}} *and* > adjusts {{<version>${revision}${changelist}</version>}} to e.g. > {{{}<version>1.29</version>{}}}. > h3. Actual results > Starting with Maven Release Plugin 3.1.0, the {{[maven-release-plugin] > prepare release}} commit still adjusts {{<tag>${scmTag}</tag>}} to e.g. > {{{}<tag>text-finder-1.29</tag>{}}}, but it *fails to adjust* > {{<version>${revision}${changelist}</version>}} to e.g. > {{<version>1.29</version>}} as expected. After this, the release subsequently > fails. > h3. Evaluation > This regression is caused by the changes to {{AbstractRewritePomsPhase}} made > in MRELEASE-1109. When these changes are reverted, the issue is resolved. > h3. Note > This caused the weekly Jenkins core release to fail on July 2, 2024. We have > downgraded Maven Release Plugin to 3.0.1 in order to restore stability to our > releases. -- This message was sent by Atlassian Jira (v8.20.10#820010)