Details
Description
Case:
project (version 1.0.4-SNAPSHOT)
- pom.xml with
<modules>
<module>module1</module>
<module>module2</module>
</modules>
project/module1 (version 1.0.4-SNAPSHOT) - pom.xml with "project" as its parent
- dependency on module2
project/module2 (version 1.0.4-SNAPSHOT) - pom.xml with "project" as its parent
In the "project" folder run
- mvn -DdryRun=true release:prepare -DpreparationGoals=clean
=> release version: 1.0.4
=> next dev version: 1.0.5-SNAPSHOT
Result:
- "project" pom has two correct pom versions: pom.xml.tag & pom.xml.next
- "module" pom:
- correct pom.xml.tag, meaning:
=> correct parent/version: 1.0.4-SNAPSHOT
=> correct module2 dependency moved from 1.0.4-SNAPSHOT to 1.0.5-SNAPSHOT - pom.xml.next:
=> correct parent/version: 1.0.5-SNAPSHOT
=> wrong module2 dependency 1.0.4-SNAPSHOT (it should be 1.0.5-SNAPSHOT)
Attachments
Attachments
Issue Links
- supercedes
-
MRELEASE-295 Internal dependencies left at old snapshot
- Closed