Improve snapshot dependency handling of parent artifacts
--------------------------------------------------------
Key: MRELEASE-588
URL: http://jira.codehaus.org/browse/MRELEASE-588
Project: Maven 2.x Release Plugin
Issue Type: Improvement
Components: prepare
Affects Versions: 2.0
Reporter: Elliot Metsger
This builds on the patch in MRELEASE-583, where the user is prompted for the
release version of snapshot dependencies.
However, when the snapshot dependency to be resolved is the parent artifact of
the project being released, the version supplied by the user is not used in the
transformed release version of the pom.
For example, I want to release the following:
{code}
<project>
<groupId>org.dataconservancy</groupId>
<artifactId>project-pom</artifactId>
<version>1.0.0-SNAPSHOT</version>
<parent>
<groupId>org.dataconservancy</groupId>
<artifactId>parent-pom</artifactId>
<version>1.0.0-SNAPSHOT</version>
</parent>
...
</project>
{code}
If I have MRELEASE-583 applied, I go through the snapshot resolution dialog:
{code}
There are still some remaining snapshot dependencies.: Do you want to resolve
them now? (yes/no) no: : yes
Dependency type to resolve,: specify the selection number ( 0:All 1:Project
Dependencies 2:Plugins 3:Reports 4:Extensions ): (0/1/2/3) 1: :
Resolve Project Dependency Snapshots.: 'org.dataconservancy:parent-pom' set to
release? (yes/no) yes: : yes
What is the release version? 1.0.0: : 1.0.0-test
{code}
The resulting release pom doesn't use 1.0.0-test as the parent version. It
uses 1.0.0:
{code}
<project>
<groupId>org.dataconservancy</groupId>
<artifactId>project-pom</artifactId>
<version>1.0.0-test</version>
<parent>
<groupId>org.dataconservancy</groupId>
<artifactId>parent-pom</artifactId>
<version>1.0.0</version>
</parent>
...
</project>
{code}
--
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
