[jira] Issue Comment Edited: (MRELEASE-6) Multiproject Release: No check in

["Christian Hall (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRELEASE-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92881 ] 

Christian Hall edited comment on MRELEASE-6 at 4/13/07 3:10 PM:
----------------------------------------------------------------

I think we are also forced to have our parent pom and our master pom (the one that has the modules defined in it) be the same pom file due to this issue. Would be nice to not require this as sometimes the master pom needs its own parentage compared to an actual component project.


 was:
One issue we have here is that we have a large platform of components and forcing the parent pom to be a standalone file at the root of our
components directory makes for a huge Subversion update to get the latest parent pom (since cannot update a single file). So, solutions that just solve the Eclipse problem don't fix it for us. 

Our directory structure is:

components/
+ pom.xml
+ component1/
+ + pom.xml
+ component2/
+ + pom.xml
...
with lots of components. I think we are also forced to have our parent pom and our master pom (the one that has the modules defined in it) be the same pom file due to this issue. Would be nice to not require this as sometimes the master pom needs its own parentage compared to an actual component project.

> Multiproject Release: No check in
> ---------------------------------
>
>                 Key: MRELEASE-6
>                 URL: http://jira.codehaus.org/browse/MRELEASE-6
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-5
>         Environment: Windows XP, Eclipse Workspace
>            Reporter: Bernd Mau
>            Assignee: Jason van Zyl
>            Priority: Critical
>             Fix For: 2.0-beta-5
>
>
> 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