2009/3/23 Barrie Treloar <baerr...@gmail.com>

> On Mon, Mar 23, 2009 at 11:37 PM, Olivier Lamy <ol...@apache.org> wrote:
> > Hi,
> > A very famous issue ! http://jira.codehaus.org/browse/MRELEASE-375
> >
> > My next days jobs will be releasing maven-scm and release-plugin :-))
>
> yes i saw that but didn't click that running the below command with
> 1.5.6 was hanging becuase of it...
>
> Upgrading to 1.6.0 svn fixes the manual delete issue:
>
> But mvn release:prepare still failed (using svn 1.6.0).
>
> Do you know why that is?
>

Because when you use the neon transport for a http or a https based
repository, there is a bug in neon that prevents tagging from the working
copy unless the working copy is at the head revision.

You could do any of the following:

1. Switch to using the dav_serf for your http or https repository (This is
reported to work but I have not had an oportunity to test it)

2. Use a script something like this

mvn release:prepare release:perform $*
svn update
mvn release:prepare release:perform $*

You can make the script all fancy checking return values and searching the
release.properties file for one of the two phases where it breaks (scm-tag
and another phase which I do not have to hand)

I'll post my unix and windows scripts for running a release when I get into
work tomorrow.


>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Reply via email to