Comments within. --- Todd Thiessen
> -----Original Message----- > From: sverhagen [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 09, 2008 6:07 PM > To: [email protected] > Subject: Up-to-date release > > > Hi. We heavily use the Maven release plugin. > Following scenario: > * Developers update from SVN > * Developer 1 commits a change > * Developer 2 commits a change and releases ("mvn release:prepare") > > Because developer 2 does not explicitly update from SVN, the > change from developer 1 will not be in the release. Hard to > track down, hard to detect. Why would you expect developer 1's changes to be in the release? If developer 2 does a check out, makes a change then builds a release he should NOT expect developer 1's changes since he never performed an update. The release plugin should NOT do an update automatically. At most this should be an option but I think it is just fine having developer 2 having to run a svn update if he/she wishes to get the latest commits. This causes fewer "freezes" of the main trunk. Someone can do a formal release and other devs can still commit to trunk and only see those changes in SNAPSHOT versions where they can get some soak before making a formal release. Once the release checkout is made, what is in the working copy should be exactly what is released. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
