[
https://jira.codehaus.org/browse/MRELEASE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=301579#comment-301579
]
James Levinson edited comment on MRELEASE-565 at 6/20/12 4:50 PM:
------------------------------------------------------------------
confirming that I am seeing this in versions 2.2.2 and 2.3.2 with maven-2.2.1 &
maven-3.0.3. Also, the tag that is created in the perform leaves a SNAPSHOT
version in the pom. So, the next pom is not being incremented or prompted for
and the tag is not being firmed up. I suppose those are pert of the same
process.
was (Author: jamlev1):
confirming that I am seeing this in versions 2.2.2 and 2.3.2. Also, the tag
that is created in the perform leaves a SNAPSHOT version in the pom. So, the
next pom is not being incremented or prompted for and the tag is not being
firmed up. I suppose those are pert of the same process.
> CLONE -Updating of dependencyManagement inconsistent with updating of
> dependencies with regard to SNAPSHOTs
> -----------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-565
> URL: https://jira.codehaus.org/browse/MRELEASE-565
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: maven 2.0.4, win XP
> Reporter: Carlo de Wolf
> Assignee: Emmanuel Venisse
>
> The mechanism in release:prepare for creating the new development version of
> POM's handles snapshots that are part of the current reactor build
> differently for dependencyManagement and for dependencies.
> A snapshot version in a dependencies section will be updated to the next
> development version whereas one in dependencyManagement won't.
> The attached patch will change this behavior. It will update a snapshot
> version under dependencyManagement if and only if it is part of the current
> reactor build.
> Note that dependencies cannot contain snapshot versions that are not part of
> the current reactor, but dependencyManagement can. I suggest to forbid this
> too.
> A second suggestion is to introduce a parameter to control the updating of
> snapshot dependencies in both dependencyManagement and dependencies sections.
> Either leave them at the released version or update them to the new
> development version. This touches on the discussion in MRELEASE-36 about the
> developer having to knowingly choose to use a new development version. I
> would be fine with using a parameter to select the behavior as obtained with
> my patch. My central point is that dependencyManagement and dependencies
> snapshots should behave the same.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
