-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm subscribed to this bug:
http://jira.codehaus.org/browse/SCM-406 Lots of people are complaining, but sadly there are no answers so far. The problem seems to be that when doinf releaase:prepare, the release plugin tries to commit the current working copy as a tag, instead of copying a remote URL. SVN < 1.5 allows this, SVN 1.5.x apparently does not. There's bound to be a workaround. Someone suggested locking the trunk while the release plugin runs; I have no idea how feasible that would be. sverhagen wrote: > > Stephen Connolly-2 wrote: >> Use Subversion 1.5 >> >> the release plugin is broken with svn 1.5 and will not make a release if >> the >> entire workspace is not 100% up to date > > Hi, Stephen. Thanks for your prompt reply, but I tend to disagree. I am > having exactly the problems that I described while being on 1.5.0 (see > below). There is some regression in Subversion, I suppose, I have had people > downgrade back to 1.5.0 for not being to able to release. Would you have the > JIRA issue for what you're referring to? > Thanks, Sander. > > "svn --version" > svn, version 1.5.0 (r31699) > compiled Jun 23 2008, 12:59:48 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEUEARECAAYFAkk/R68ACgkQ0GFaTS4nYxsnTACXWccUsTP0D7DPnN8fxTOgJE07 PgCfQjLqI5xMbRpfhMn/Zac5ktQnJhw= =enWc -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
