[ http://jira.codehaus.org/browse/MRELEASE-6?page=comments#action_57634 ]
Kenney Westerhof commented on MRELEASE-6: ----------------------------------------- One more thing: only <type>pom</type> projects can have modules. So I don't see any reason not to add a root pom that specifies your four modules. That way you can have a normal tree with the modules as direct children (in the sub-directory-sense) as was intended: master/ /hhla.... /hhla... Since the master would have packaging pom, it won't get included in eclipse, since it does not produce any artifacts. I do this all the time and have absolutely no problems with it. > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
