The scm config looks like:
<scm>
<connection>
scm:svn:svn+ssh://galatea.chrissearle.org/repository/common/trunk
</connection>
<developerConnection>
scm:svn:svn+ssh://galatea.chrissearle.org/repository/common/trunk
</developerConnection>
</scm>
The plugin is configured
<plugin>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<tagBase>
svn+ssh://galatea.chrissearle.org/repository/common/tags
</tagBase>
</configuration>
</plugin>
mvn release:prepare run as a dry run seems to create the new poms
just fine (the pom.xml.tag gets a /common/tags/common-1.0 end to its
URL).
But - if I run it non dry run it complains: [INFO] Checking in modified POMs...[INFO] Executing: svn --username chris --non-interactive commit -- file /tmp/maven-scm-1341137195.commit --targets /tmp/maven-scm-40186- targets
[INFO] Working directory: /Users/chris/src/java/common [INFO] Tagging release with the label common-1.0...[INFO] Executing: svn --username chris --non-interactive copy --file / tmp/maven-scm-449764955.commit . svn+ssh:// [EMAIL PROTECTED]/repository/common/tags/common-1.0
[INFO] Working directory: /Users/chris/src/java/common[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE[INFO] ------------------------------------------------------------------------
[INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow):svn: Source url 'svn+ssh://galatea.chrissearle.org/repository/common/ trunk' is from different repository
The only thing I can spot is in that Tagging line - where it has inserted the username into the SCM URL.
I'm a tad confused (this is my first attempt at getting the release plugin involved - so I may well have screwed up something.
Any hints as to what I may be missing/have wrong in my config? Chris Searle [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
