[ 
http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211045#action_211045
 ] 

Damien Coraboeuf commented on MRELEASE-526:
-------------------------------------------

So:
* I added the <connection> URL in the parent POM (same as developer connection 
actually)
* I switched back to the maven-release-plugin 2.0 version (in the plugin 
management section)

The tag is created from the project/

When I use the maven-release-plugin 2.0.9 version, the tag is created from the 
trunk.

Here is an extract of the parent POM about the release plug-in configuration:

{noformat}
        <build>
                <pluginManagement>
                        ...
                        <plugins>
                                <plugin>
                                        
<groupId>org.apache.maven.plugins</groupId>
                                        
<artifactId>maven-release-plugin</artifactId>
                                        <version>2.0</version>
                                </plugin>
                        </plugins>
                        ...
                </pluginManagement>
                <plugins>
                        ...
                        <plugin>
                                <groupId>org.apache.maven.plugins</groupId>
                                <artifactId>maven-release-plugin</artifactId>
                                <configuration>
                                        <remoteTagging>true</remoteTagging>
                                </configuration>
                        </plugin>
                        ...
                </plugins>
        </build>
{noformat}

> release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of 
> project/trunk
> -------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-526
>                 URL: http://jira.codehaus.org/browse/MRELEASE-526
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0
>         Environment: Maven 2.2.1
>            Reporter: Damien Coraboeuf
>            Priority: Critical
>
> We have switched to the release plug-in 2.0 and are using the prepare goal as 
> we did before using version 2.0-beta-9. Unfortunately, the tag which is now 
> created is copied from the project level, and from the trunk. With version 
> 2.0-beta-9, the tag was correctly copied from the trunk.
> With 2.0-beta-9:
> {noformat}
>  /project
>    |-- trunk/
>          |-- pom.xml
>          |-- src/
>    |-- tags/
>          |-- 4.0.1/ (<-- copied from trunk
>               |-- pom.xml
>               |-- src/
> {noformat}
> With 2.0:
> {noformat}
>  /project
>    |-- trunk/
>          |-- pom.xml
>          |-- src/
>    |-- tags/
>          |-- 4.0.1/ (<-- copied from trunk
>               |-- trunk/
>                    |-- pom.xml
>                    |-- src/
>               |-- tags/
>               |-- branches/
> {noformat}
> Our _pom.xml_ SCM information is declared as follow:
> {noformat}
> <scm>
>       
> <developerConnection>scm:svn:svn://host/path/project/trunk</developerConnection>
> </scm>
> {noformat}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to