Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Won't Fix
-
2.1
-
None
Description
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
Attachments
Attachments
Issue Links
- is duplicated by
-
MRELEASE-656 Unable to release multi-module project with pom module referencing a property inheriting from the parent&aggregator root pom
- Closed
- relates to
-
MRELEASE-666 release:prepare can fail during rewrite-poms-for-development phase if a property matches the version being released
- Closed