Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
2.1
-
None
-
None
-
Linux
Description
Executing
mvn release:prepare -DautoVersionSubmodules=true -Pci
against http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/ @r35313 in order to create http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-3.0-milestone-3/ fails with the attached log (I attached only the final part of the console log) when using 3.0-milestone-3 as release version. Prepare succeeds if release version is 3.0-test-3. In other words release:prepare fails if the version being released matches the commons.version property defined in the parent pom. Note that after release:prepare fails all poms are ready to be committed, i.e. I just had to commit them to finish the release:prepare , so it looks like release:prepare manages to rewrite the poms for next development iteration but fails just before committing them for some obscure reason.
I was able to reproduce this with both maven 2.2.1 and 3.0.3.
Attachments
Attachments
Issue Links
- is related to
-
MRELEASE-217 BUILD FAILURE: The version could not be updated: ${version}
- Closed
-
MRELEASE-657 Unable to release multi-module project with pom module referencing a property coming from the parent&aggregator root pom as a dependency version : "The version could not be updated: ${...}"
- Closed