Graham Leggett wrote: > > Jose Alberto Fernandez wrote: > >> 1) When we do a release, the SVN "label" for the release must be located >> on >> the branches/ directory of SVN. This is because the plugin creates the >> "label", then changes the POMs to remove the SNAPSHOT and then tries to >> commit. By default committing on the tags/ directory is not allowed. As a >> result we finish with lots of branches/* and we really cannot easily >> distinguish any more between a release and a development branch. >> >> Are we using SVN or maven wrong? What is the best practice for this? > > By default, the "release:prepare" step creates the release in the /tags > directory. > > Branches go by default in /branches, giving you the separation you want. > > Double check your config to make sure you are not overriding any defaults. > > Regards, > Graham > -- > >
Thanks Graham, The problem we had when using the default configuration is that SVN by default does not allow you to make commits on the tags/ directory. As they are supposed to be fix images of the code at a particular point in time. As I understand SVN commit has a constraint set up by default to stop you from making any commits on the tags/ directory. Does one has to disable this constraint in order to be able to work with the release plugin as configured by default? Without removing the constraint, the release plugin would have to commit lets say on trunk the POMs to the version being released, make the label on tags/ and then update the POMs again on trunk to the new snapshot version and commit again. But that does not seem to be what the release plugin is doing. It seem to be changing the POMs to the fixed version on the label on tags/. am I mistaken? Or are we using something wrongly? We are using maven-release-plugin:2.0-beta-4. -- View this message in context: http://www.nabble.com/Release-Plugin---svn-tags-and-branches-tf4206590s177.html#a11981210 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
