You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Cornel Masson (JIRA)" <ji...@codehaus.org> on 2010/09/08 18:20:32 UTC

[jira] Issue Comment Edited: (MRELEASE-562) release:prepare uses incorrect tag source on multi-module projects

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

Cornel Masson edited comment on MRELEASE-562 at 9/8/10 11:19 AM:
-----------------------------------------------------------------

I have the same problem.

When release:prepare creates the new tag, the contents is not a copy of what trunk was at the time, but what the *parent* dir of trunk was.

Our SVN repo has projects at the top level, and each project has trunk, branches and tags below that. Surely such a structure is supported? I specify the tagBase explcitly when running release:prepare.

{code}
svnhost/code/server/projectA:
 /trunk
 /branches
 /tags

svnhost/code/server/projectBB:
 /trunk
 /branches
 /tags
{code}

When I release:prepare say projectA and specify tag "MyTag" it ends up like this:

{code}
svnhost/code/server/projectA:
 /trunk
 /branches
 /tags
    /MyTag
       /trunk
       /branches
       /tags
          /...all tags prior to MyTag...
{code}

??

      was (Author: cornel.masson):
    I have the same problem.

When release:prepare creates the new tag, the contents is not a copy of what trunk was at the time, but what the *parent* dir of trunk was.

Our SVN repo has projects at the top level, and each project has trunk, branches and tags below that. Surely such a structure is supported? I specify the tagBase explcitly when running release:prepare.

svnhost/code/server/projectA:
 /trunk
 /branches
 /tags

svnhost/code/server/projectBB:
 /trunk
 /branches
 /tags

When I release:prepare say projectA and specify tag "MyTag" it ends up like this:

svnhost/code/server/projectA:
 /trunk
 /branches
 /tags
    /MyTag
       /trunk
       /branches
       /tags
          /...all tags prior to MyTag...

??
  
> release:prepare uses incorrect tag source on multi-module projects
> ------------------------------------------------------------------
>
>                 Key: MRELEASE-562
>                 URL: http://jira.codehaus.org/browse/MRELEASE-562
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0
>            Reporter: Juven Xu
>
> source code layout:
> svn://host/app/pom.xml (aggregator)
> svn://host/app/app-parent/pom.xml (parent)
> svn://host/app/app-module-a/pom.xml
> svn://host/app/app-module-b/pom.xml
> run mvn release:prepare in the aggreagtor foler, I see output like this:
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive copy --file C:\Users\JUVEN\AppData\Local\Temp\maven-scm-2081030526.commit --revision 25 svn://192.168.1.103/app/ svn://192.168.1.103/app/tags/app-aggregator-1.0.0"
> the tag source should be svn://192.168.1.103/app/trunk
> similar issue was reported in maven user list: http://old.nabble.com/multi-modules,-scm-and-release-plugin-td28289933.html

-- 
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