Jose Alberto Fernandez <[EMAIL PROTECTED]> writes: > > 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. > Hello Jose, I am pretty sure that whatever is preventing you from commiting to tags/ directory is some particular configuration of subversion's repository (hooks maybe ?) or the tool you are using (I remember that tortoisesvn warns you about this).
Here are some test case (linux ubuntu feisty): $> svn --version svn, version 1.4.3 (r23084) $> svnadmin create dummy $> mkdir work $> cd work $> svn co file:///home/nono/dummy/ $> cd dummy/ $> svn mkdir tags branches trunk $> cd trunk/ $> cat > foo something ^D $> svn add foo $> cd .. $> svn ci -m "initial" $> cd .. $> rm -fr dummy/ $> svn cp file:///home/nono/dummy/trunk file:///home/nono/dummy/tags/1 $> svn co file:///home/nono/dummy/tags/1 dummy $> cd dummy/ ls $> cat > bar something else ^D $> svn add bar $> svn ci -m "commit in tag" $> svn list -R file:///home/nono/dummy branches/ tags/ tags/1/ tags/1/bar tags/1/foo trunk/ trunk/foo It is however possible to make a svn cp from the working copy to an URL, which means that you can have local modifications be propagated to a remote copy without actually having to check-in in the tags/ or whatever target location you are using. My 2 cts. -- OQube < software engineering \ génie logiciel > Arnaud Bailly, Dr. \web> http://www.oqube.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
