[MRELEASE-389] Properties releaseVersion and developmentVersion are not read correctly during release:prepare (eventually release:perform)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 2.0-beta-8
• Component/s: prepare
• Environment: Maven version: 2.0.9; Java version: 1.6.0_07; OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"; scm=CVS
• Flags: Patch
• Assignee: Paul Gier
• Reporter: Jean-Claude Rouvinez
• Created: 21/Nov/08 05:54
• Updated: 05/Apr/15 14:53
• Resolved: 18/Aug/09 10:22

Description

Calling
mvn --batch-mode release:prepare release:perform -Dtag=TEST_RELEASE-3_0_0 -DreleaseVersion=3.0.0 -DdevelopmentVersion=3.0.1-SNAPSHOT
doesn't produce the expected results:

• -DdevelopmentVersion=3.0.1-SNAPSHOT
  • the value is not set correctly in the file pom.xml:
    • Expected: <version>3.0.1-SNAPSHOT</version>
    • But was: <version>2.0.5-SNAPSHOT</version>

• -DreleaseVersion=3.0.0
  • the artifacts are not created correctly:
    • Expected artifact: ipi-multimodule-b-3.0.0.jar
    • But was: ipi-multimodule-b-2.0.4.jar
  • the value is not set correctly in the file pom.xml (comment in CVS: [maven-release-plugin] prepare release TEST_RELEASE-3_0_0):
    • Expected: <version>3.0.0</version>
    • But was: <version>2.0.4</version>

• -Dtag=TEST_RELEASE-3_0_0
  • the value is set correctly in the file pom.xml
  • the tagging of the CVS module is also correct.

Issue Links

• is related to: MRELEASE-128 SCM properties being replaced during release:perform
• is related to: MRELEASE-173 Allow command line specification of versions
• relates to: MRELEASE-387 command line versions don't seem to work on release:branch