Maven-release-plugin and maven 3.0.3

Question

I am using the release maven plugin to do the following with maven-3.0.3

mvn release: prepare

Everything seems fine except that when it creates a tag in SVN, it copies the previous version from the tag folder with the correct label. Any ideas why?

If I return to maven-2.2.1, then the tagging will be correct and the content of the tags will be expected.

With Maven 2.2.1:

[INFO] Tagging release with the label crcib-6.8.5... [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file c:\DOCUME~1\markand\LOCALS~1\Temp\maven-scm-1593649573.commit . <url>/svn/repos/crcib/tags/crcib-6.8.5" 

With Maven 3.0.3:

 [INFO] Tagging release with the label crcib-6.8.5... [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file c:\DOCUME~1\markand\LOCALS~1\Temp\maven-scm-2047728233.commit --revision 6331 <url>/svn/repos/crcib/tags/crcib-6.8.2 <url>/svn/repos/crcib/tags/crcib-6.8.5" 

Any ideas why? In addition, it seems that when using Maven 2, several artifacts are loaded before starting tagging. This does not apply to Maven 3.

Answer 1

Without your pom.xml it's hard to understand what the problem is.

The most obvious misconfiguration probably relates to scm, as Wemu said;

 <scm> <!-- Base URL of repository (trunk/tags/branches independant)--> <url>scm:svn:http://svn.my.company.com/repository</url> <!-- Current working url (NOT TAG ONE) --> <connection>scm:svn:http://svn.my.company.com/repository/trunk/my-project</connection> <!-- Current working url --> <developerConnection>scm:svn:http://svn.my.company.com/repository/trunk/my-project</developerConnection> </scm> 

This is the version and how I use this plugin:

  <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-release-plugin</artifactId> <version>2.2.2</version> <configuration> <tagBase>svn.my.company.com/repository/tags</tagBase> </configuration> </plugin> 

When you use the maven release plugin, it will change your scm configuration to point to tags. If this is really a maven 3 problem, I never noticed it.

Could you post pom.xml (and settings.xml) for further analysis?