[
http://jira.codehaus.org/browse/MRELEASE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235569#action_235569
]
Marcus Linke edited comment on MRELEASE-588 at 9/17/10 2:47 AM:
----------------------------------------------------------------
I think a should give it a try... ;) For what version is your patch for? I
suggest to merge the patches from MRELEASE-583, MRELEASE-588 and MRELEASE-350
into one. After that the discussed changes from MRELEASE-583 (improved version
prompting) could be implemented. But i dont know if this is desired by the core
developer. Any comments?
was (Author: mlinke):
I think a should give it a try... ;) For what version is your patch for? I
suggest to merge the patches from MRELEASE-583, MRELEASE-588 and MRELEASE-350
into one. After that the discussed changes from MRELEASE-588 (improved version
prompting) could be implemented. But i dont know if this is desired by the core
developer. Any comments?
> 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
> Fix For: 2.1
>
> Attachments: Dependency_handling_of_parent_artifacts.patch
>
>
> 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
