[ 
https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297036#comment-297036
 ] 

Vedavyas Panneershelvam edited comment on MRELEASE-679 at 4/23/12 9:03 AM:
---------------------------------------------------------------------------

Using Maven version 3.0.3 and Maven Release Plugin version from (2.0 - 2.2), 
the content of the created tag includes branches, tags and trunk instead of the 
contents of trunk alone.
    
The SCM structure is
    Repo
      |-- branches
      |-- tags
      |-- trunk
            |-- parent
            |-- module1
            |-- module2
            |-- etc
The parent-pom.xml aggregates the child modules and all the child modules refer 
the parent module as the parent. 
And Frans suggestion of passing -DConnectionUrl didn't work either.

                
      was (Author: ved):
    Using Maven version 3.0.3 and Maven Release Plugin version from (2.0 - 
2.2), the content of the created tag includes 
    |-- branches
    |-- tags
    |-- trunk
The SCM structure is
    Repo
      |-- branches
      |-- tags
      |-- trunk
            |-- parent
            |-- module1
            |-- module2
            |-- etc
The parent-pom.xml aggregates the child modules and all the child modules refer 
the parent module as the parent. 
And Frans suggestion of passing -DConnectionUrl didn't work either.

                  
> CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ 
> instead of project/trunk
> --------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-679
>                 URL: https://jira.codehaus.org/browse/MRELEASE-679
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0
>         Environment: Maven 2.2.1
>            Reporter: Claus Gebert
>            Assignee: Brett Porter
>            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, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to