[ 
https://jira.codehaus.org/browse/MRELEASE-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323739#comment-323739
 ] 

Thorsten Heit commented on MRELEASE-181:
----------------------------------------

There are at least two patches for release:prepare for this feature:
* MRELEASE-835
* MRELEASE-463
                
> During the release:prepare goal this plugin should check if released versions 
> of SNAPSHOT dependencies exist before failing.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-181
>                 URL: https://jira.codehaus.org/browse/MRELEASE-181
>             Project: Maven 2.x Release Plugin
>          Issue Type: Improvement
>          Components: prepare
>         Environment: All
>            Reporter: Gregory Scott
>
> During the release:prepare goal this plugin should check if released versions 
> of SNAPSHOT dependencies exist before failing.
> When working in an environment where multiple modules are apart of the 
> release it becomes time consuming to update each module with the correct 
> version.
> For Example:
> Lets say you have 3 projects A, B, and C. Project A depends on B and C. 
> Project B depends on C. All projects are at version x-SNAPSHOT. All projects 
> have been tested and are ready for release. I run through the release process 
> for Project C and version x is now deployed to the repository and ready for 
> use. I then go to do the release for Project B the current release plugin 
> fails because it says my POM is still referencing project C version 
> x-SNAPSHOT. Oops okay I'll have to update the POM to use project C version x. 
> This goes on an on. It would be nice for the plugin to realize that there is 
> a SNAPSHOT dependency but goes and checks the repository for a released 
> version of that SNAPSHOT; if found update the POM accordingly and continue 
> with the release process.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to