[jira] Closed: (MRELEASE-319) Release Tag does not contain Modules

["Lou S (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MRELEASE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lou S closed MRELEASE-319.
--------------------------

    Resolution: Duplicate

Duplicate of MRELEASE-261

> Release Tag does not contain Modules
> ------------------------------------
>
>                 Key: MRELEASE-319
>                 URL: http://jira.codehaus.org/browse/MRELEASE-319
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-7
>         Environment: win32, SVN
>            Reporter: Lou S
>
> When attempting to release a project using this plugin I notice that the interaction works fine with SVN with the exception of creating the tag properly.  I notice that the project I'm running from (i.e., the parent maven project) will post only its contents to the tag, but not its modules.
> My project directory looks something like:
> MavenProject
> CommonProject
> DaoProject
> WebProject
> The MavenProject directory contains the master pom.xml and the other directories are children, so my modules tag looks like: 
> 	<modules>
> 	    <module>../CommonProject</module>
> 	    <module>../DaoProject</module>
> 	    <module>../WebProject</module>
>         </modules>
>  
> The command I run is as follows:
> mvn -Penv-prd -Dlabel=PRD.BLD.1.0.0.69 -Dusername=lsacco -Dpassword=xxxx -DdryRun=true -DautoVersionSubmodules=true
>  release:prepare
> The expected result is that the Parent and child modules would be copied and tagged based on the contents of the POM and the label I provide at runtime.

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