Same error for me with SVN 1.5.1 on windows. It's not a MAC only issue Coming back to 1.4.6 solves the issue
Arnaud On Tue, Aug 26, 2008 at 5:17 PM, Glase, Stefan < [EMAIL PROTECTED]> wrote: > Hello David, > > I just updated to Subversion version 1.5.1 (r32289) and now i am running > into the same problem as you. > > Stephen refered to similar issues today in this list. > > Regards > Stefan > > > -----Ursprüngliche Nachricht----- > Von: David Roussel [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 26. August 2008 16:39 > An: users@maven.apache.org > Betreff: Re: AW: Release fails during SVN commit > > > Stefan, > > If it works for you, is it because it's a single module with no nested > modules? > > I have maven 2.0.9, svn 1.5.1 (trigis.org build), Java 1.6.0_06, Windows > XP > SP2, > > It's interesting that the command that fails: > > svn --non-interactive copy --file > C:\DOCUME~1\UT159N\LOCALS~1\Temp\maven-scm-1777868452.commit . > http://svnserver/svn/REPO1/Projects/InstallTools/tags/installer-0.5 > > also fails if I run it manually, but if I run 'svn up' then rerun it, it > works. > > It's as if the previous commit has not updated the working copy in someway. > > I tried to reproduce the problem in pure svn commands, creating a new repo, > adding files, tagging, then going back to a previous revision, then tagging > again. But I was unable to reproduce it. > > Perhaps there is a way to get the SCM plugin to log every command it runs, > see which step is not updating the working copy. > > Thanks > > David > > > > Glase, Stefan wrote: > > > > Hi Andreas, > > > > I am not sure but maybe this would be worth a try. > > > > In my projects I always refer to the trunk folder in the SCM > configuration > > and point to the tags or releases folder in the tagBase property of the > > maven-release-plugin. > > > > So your configuration would look like this in your pom.xml: > > > > <scm> > > <connection>scm:svn:http://xxx/svndir/project/trunk</connection> > > <developerConnection>scm:svn:http://xxx > > /svndir/project/trunk</develope > > rConnection> > > <url>http://xxx /svndir/project/</url> > > </scm> > > > > ... > > > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-release-plugin</artifactId> > > <configuration> > > <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase> > > <autoVersionSubmodules>true</autoVersionSubmodules> > > <preparationGoals>clean install</preparationGoals> > > </configuration> > > </plugin> > > > > My idea behind this is, that it might be a problem to point to a > > tag-directory within the scm connection. I my understanding those folders > > should be on the same level. > > > > Hope to help > > Stefan > > > > -----Ursprüngliche Nachricht----- > > Von: Andreas Heinecke [mailto:[EMAIL PROTECTED] > > Gesendet: Donnerstag, 21. August 2008 10:04 > > An: users@maven.apache.org > > Betreff: Release fails during SVN commit > > > > Hi there, > > > > I encountered a strange problem. Since a few weeks I'm not able to > perform > > a > > release with Maven. The release process fails during executing the > > release:prepare goal at the same position, always. The point at which the > > release fails is when Maven tries to commit the release POM's to SVN. > This > > commit fails with the error message that the file which is about to be > > committed already exists at the position in SVN. But it isn't there. > > Strange, uh? > > > > I actually checked the tagbase configuration of the plugin and tried to > > alter it, but the effect remains. > > I don't know what I can try to fix this issue. > > The last thing altered at the configuration is a switch of the SVN > server. > > We had to switch to a newer SVN version 1.5.0. We also switched to the > new > > 1.5.0 SVN client as we know that there are problems with newer server > > software and older client software. > > > > Please find parts of my pom.xml configuration attached below. > > > > Any pointers are welcome. > > > > Regards, > > Andreas. > > > > My SCM configuration: > > <scm> > > <connection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project > </connection> > > > > <developerConnection>scm:svn:http://xxx.xxx.xxx.xxx/svndir/project > </develope > > rConnection> > > <url>http://xxx.xxx.xxx.xxx/svndir/project</url> > > </scm> > > > > My release plugin configuration: > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-release-plugin</artifactId> > > <configuration> > > <tagBase>http://XXX.XXX.XXX.XXX/svndir/project/tags</tagBase> > > <autoVersionSubmodules>true</autoVersionSubmodules> > > <preparationGoals>clean install</preparationGoals> > > </configuration> > > </plugin> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/Release-fails-during-SVN-commit-tp19084270p19163336.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .......................................................... Arnaud HERITIER .......................................................... OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .......................................................... ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...........................................................
