[MRELEASE-642] prepare tags the wrong source

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Auto Closed
• Affects Version/s: 2.1
• Component/s: prepare-with-pom
• Assignee: Unassigned
• Reporter: Anthony Ogier
• Created: 04/Feb/11 05:12
• Updated: 06/Sep/15 20:44
• Resolved: 06/Sep/15 20:44

Description

The use case is mostly defined here

Here is our svn structure :

trunk/
 +- docs/
 +- dev/
     +- project-parent/
         +- pom.xml
     +- project-war/
         +- pom.xml
releases/

When preparing the release (mvn release:prepare-with-pom), I want to tag trunk/dev/ into releases/project-<release-version>/.

The parent pom.xml is like this :

<build>
    <plugins>
        <plugin>
            <artifactId>maven-release-plugin</artifactId>
            <version>2.1</version>
            <configuration>
                <tagBase>http://svn.mycompany.com/svn/project/releases</tagBase>
                <generateReleasePoms>false</generateReleasePoms>
                <autoVersionSubmodules>true</autoVersionSubmodules>
            </configuration>
        </plugin>
    </plugins>
</build>

<scm>
    <connection>scm:svn:http://svn.mycompany.com/svn/project/trunk/dev</connection>
    <developerConnection>scm:svn:http://svn.mycompany.com/svn/project/trunk/dev</developerConnection>
    <url>scm:svn:http://svn.mycompany.com/svn/project/trunk/dev</url>
</scm>

My working copy /home/user/project is checked out from http://svn.mycompany.com/svn/project/trunk/.

When doing mvn release:prepare-with-pom -DdryRun=true, it says me that :

[INFO] Full run would be tagging working copy /home/user/project/dev with label: 'project-<release-version>'

But, when removing -DdryRun=true, here is what the plugin does :

[INFO] Executing: /bin/sh -c cd /home/user/project/dev/project-parent && svn --non-interactive commit --file /tmp/maven-scm-1922580928.commit --targets /tmp/maven-scm-8496598021737984450-targets
[INFO] Working directory: /home/user/project/dev/project-parent
[INFO] Tagging release with the label project-<release-version>...
[INFO] Executing: /bin/sh -c cd /home/user/project/dev && svn --non-interactive copy --file /tmp/maven-scm-982655546.commit --revision <revision> http://svn.mycompany.com/svn/project/trunk http://svn.mycompany.com/svn/project/releases/project-<release-version>
[INFO] Working directory: /home/user/project/dev

So, with dryRun we think that it is trunk/dev which will be tagged, and when doing a real prepare, it is finally trunk/ which is tagged, and this is not espected.

Issue Links

• is related to: MRELEASE-562 release:prepare uses incorrect tag source on multi-module projects
• is related to: MRELEASE-595 release:prepare using old SVN structure when creating tag
• is related to: MRELEASE-609 release:prepare fails while trying to tag SVN with wrong URL