On Fri, August 3, 2007 12:59 pm, Jose Alberto Fernandez wrote:

> 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?

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.

Then the branch/trunk version number is bumped again to the next version
number up, and the SNAPSHOT is added back to the version number. This
change is then committed to the branch.

> 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.

This is exactly what the release plugin does.

> 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.

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.

Regards,
Graham
--



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to