[jira] Commented: (MRELEASE-6) Multiproject Release: No check in

["Fabian Bauschulte (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-6?page=comments#action_62756 ] 

Fabian Bauschulte commented on MRELEASE-6:
------------------------------------------

I am using CVS and eclipse (workspace). All my projects are CVS modules: parent and moduleA, modulesB, moduleC:
\parent
\moduleA
\moduleB
\moduleC
Every project has the section "<scm><developerConnection>xxx</developerConnection></scm>" set to the correct cvs location. Refactoring of the package structure is not possible in my case (legacy system).
I don´t see a way to use the multiproject release - any solution would be highly appreciated.

At the moment I am forced to release all modules "my hand":
\parent\mvn -N release:prepare release:perform
\moduleA\mvn release:prepare release:perform
\moduleB\mvn release:prepare release:perform
\moduleC\mvn release:prepare release:perform

Is there any chance to get this bug fixed in the next time??

> Multiproject Release: No check in
> ---------------------------------
>
>          Key: MRELEASE-6
>          URL: http://jira.codehaus.org/browse/MRELEASE-6
>      Project: Maven 2.x Release Plugin
>         Type: Bug

>  Environment: Windows XP, Eclipse Workspace
>     Reporter: Bernd Mau
>     Priority: Critical

>
>
> I tried to release a multiproject with 5 modules (on a Branch). Well,
> the POMs of all modules are changed and there are some dependencies
> which have been updated correctly. But only the master has been checked
> in correctly.
> I'm changed the recommended layout, to fit in an eclipse workspace. I
> have one master at the same level as the other modules.
> The module section of the master pom.xml:
>   <modules>
>     <module>../hhla.library.pom</module>
>     <module>../hhla.library.site</module>
>     <module>../hhla.lang</module>
>     <module>../hhla.common.log4jx</module>
>   </modules>

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