[
https://jira.codehaus.org/browse/MRELEASE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-444.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> Prepare in multi-module project update the snaphsot version to release
> version only in one of the submodule
> -----------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-444
> URL: https://jira.codehaus.org/browse/MRELEASE-444
> Project: Maven Release Plugin
> Issue Type: Bug
> Components: prepare
> Affects Versions: 2.0-beta-8
> Environment: Apache Maven 2.1.0 (r755702; 2009-03-19 04:10:27+0900)
> Java version: 1.6.0_12
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Jean-Paul GUIGUI
> Attachments: test-maven.zip
>
>
> In the case of a multi module project in which a submodule M2 is depending on
> the submodule M1, only the snapshot dependency of the submodule M2 (for
> instance D1) will be changed to release by the goal release:prepare. The
> snapshot dependencies of submodule M1 (D2) will not be automatically set to
> release into the pom.xml
> Before release:prepare
> Parent
> |-Module M1-SNAPSHOT
> | |-Dependency to D1-SNAPSHOT
> |-Module M2-SNAPSHOT
> |-Dependency D2-SNAPSHOT
> |-Dependency to M1-SNAPSHOT
> After release:prepare
> Parent
> |-Module M1
> | |-Dependency to D1-SNAPSHOT <== WRONG
> |-Module M2
> |-Dependency D2
> |-Dependency to M1
> In attachment a project. To reproduce the bug:
> mvn -f pom-dependency.xml clean install
> mvn clean install
> mvn release:prepare
> cat test-maven-dependency2/pom.xml
> Maybe related to bug MRELEASE 295
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
