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: ${...}"
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: MRELEASE-657
URL: http://jira.codehaus.org/browse/MRELEASE-657
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.1
Reporter: Baptiste MATHUS
Priority: Critical
Attachments: mreleasebug.zip, output.txt
Hi,
In our multi-modules project (same version for all modules, using
autoVersionSubmodules=true), we have added a bunch of poms that are designed to
be parent poms from other projects when using our corporate archetypes.
Those poms reference artifacts from the reactor with the same version.
To do that, we have a manually set property inside the aggregator root pom.
This version is always equal to the project version.
(We do that because we can't use ${project.version} : if we do, when someone
will use this parent pom, and they define their version, this version will be
used for the dependencies defined in the parent pom using ${project.version}).
As I'm aware this is not really simple to explain&understand, I attached a
testcase to show the problem.
I'm also attaching the resulting output.
This problem is present with both maven 3.0.2 and 2.2.1.
Cheers
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
