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]

Reply via email to