[ http://jira.codehaus.org/browse/MRELEASE-91?page=comments#action_65798 ]
Marcel Schutte commented on MRELEASE-91: ---------------------------------------- See my original comment for this issue. There is an inconsistency between handling of normal dependencies and dependencies in dependencymanagement. I would still be OK with a configuration switch to control the updating. I am not OK with this inconsistency. I don't agree with your statement that the point of releases is to move away from snapshots. As far as I know, the maven philosophy is to work on snapshots and to release fixed versions. This works very well for my usecase: a parent project that lists all dependencies and their versions in a dependencymanagement section. Fixed versions for modules external to my application and snapshots for dependencies that make up my application (ear, ejbs, wars and sometimes utility jars). The release plugin can tag and build them together with fixed versions and then increment to the next development snapshot version. > Updating of dependencyManagement inconsistent with updating of dependencies > with regard to SNAPSHOTs > ---------------------------------------------------------------------------------------------------- > > Key: MRELEASE-91 > URL: http://jira.codehaus.org/browse/MRELEASE-91 > Project: Maven 2.x Release Plugin > Type: Bug > Versions: 2.0-beta-4 > Environment: maven 2.0.4, win XP > Reporter: Marcel Schutte > Assignee: Brett Porter > Fix For: 2.0-beta-4 > Attachments: depmgnt.zip, release.patch > > > 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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
