Graham Leggett wrote: > > The release plugin doesn't ever make commits to the tags directory. > > The version number of the branch/trunk you are tagging is first bumped > from the SNAPSHOT version to a release version, the changes are committed > to the branch/trunk. > > Then the branch/trunk is tagged into the /tags directory using "svn copy", > in compliance with svn conventions. >
Hum.... What we saw was that the plugin was using "svn copy" after fixing the release version in order to commit the changes directly on the /tags directory, i.e. tagging the modified working copy. And as someone else mentioned we do have an svn hook forbidding checkins on /tags. Does any one knows if there has been a changed on the way Release plugin works on versions later that 2.0-beta4? Maybe is time for us to upgrade. > ... > > We are using the release plugin with no explicit configuration for the > release plugin in our poms, thus relying on default behaviour. > > Our version numbers are of the form x.y.z-SNAPSHOT, which is the maven > default that the release plugin can handle automatically. > > I recommend rely on the default configuration as much as you can, you will > have far fewer headaches that way. > > Well, you know that by not specifying the version of your plugins, this means that every member of your team may be using a different version? We already had problems with new guys coming into the team and getting newer versions of certain plugings that behave differently. I think that the best practice is to enforce fix versions in your POMs and make sure versions are bumped up in a consistent and well tested manner. Otherwise every developer has a potentially flawed building environment and your maven builds are not reliable any more. There is even talk about making this mandatory in maven 2.1. Jose Alberto -- View this message in context: http://www.nabble.com/Release-Plugin---svn-tags-and-branches-tf4206590s177.html#a11983564 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
