[
https://issues.apache.org/jira/browse/MRELEASE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRELEASE-565.
-----------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> CLONE -Updating of dependencyManagement inconsistent with updating of
> dependencies with regard to SNAPSHOTs
> -----------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-565
> URL: https://issues.apache.org/jira/browse/MRELEASE-565
> Project: Maven Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: maven 2.0.4, win XP
> Reporter: Carlo de Wolf
> Assignee: Emmanuel Venisse
> Priority: Major
> Attachments: example.zip, example.zip, example3.zip
>
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)
