[ http://jira.codehaus.org/browse/MRELEASE-91?page=comments#action_65805 ]
Mike Perham commented on MRELEASE-91: ------------------------------------- Marcel, I agree the inconsistency should be fixed and I would be fine with a configuration variable or switch. Let me explain my reasoning on the updating. Assume a 1.0-SNAPSHOT parent and a 1.0-SNAPSHOT modules A and B where B depends on module A 1.0-SNAPSHOT. You can release the parent and Maven will release version 1.0 of all three: parent, A and B. Now B 1.0 should depend on A 1.0. The question is should B 1.1-SNAPSHOT depend on A 1.1-SNAPSHOT or A 1.0? I believe that it should depend on the latter because nothing has changed in A yet. That why I said the developer should make the call to rev the version of A in B's pom. Now a related question is what is your release process? You seem to be indicating that you release the top-level parent and everything beneath every time. I think this is suboptimal as it will lead to spurious releases - releases in which nothing changes in a module (i.e. 1.0 and 1.1 are identical). This is another reason why I prefer to leave the dependency on A in B above at 1.0 rather than auto-incrementing it. If A doesn't change, there's no reason to release and use version 1.1. In particular this is the process we use internally here. Everything is released together once and then modules are released on an as-needed basis. Incrementing everything to the next snapshot would cause havok because we want to minimize releases and maximize backwards compatability (versioning should be explicitly controlled so we know exactly what bug or changes are made/fixed in each release). I hope this gives you a little more insight into my POV. > 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
