I used the workaround "svn up -r HEAD" to fix it... and than mvn release:prepare -Dresume=true to finish the preparation...
Got the answer with some one on here... Cheers On Fri, Jan 30, 2009 at 3:22 PM, James CE Johnson <[email protected]> wrote: > You nailed it. That box has the 1.5.3 svn client. So I can leave my > workaround in place until SVN gets fixed or roll back to 1.4. The server > is still 1.4.x so rolling back the client wouldn't be any big thing. > > Thanks for the quick info! > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > > > > What version of SVN are you using? I'm betting it's 1.5.1+. There's a > > bug where the > > release plugin can't run with SVN 1.5.1+. 1.4.x works fine, as does > 1.5.0 > > (but I hear > > that has some other bad bugs). > > > > This is a real bummer, since I would love to update to SVN 1.5, but I'm > > stuck on 1.4. > > > > I've been following the bug here: > > > > http://jira.codehaus.org/browse/SCM-406 > > > > Apparently it's an SVN thing, not an scm plugin one, but the scm bug has > a > > thorough > > discussion and links to more relevant places. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
