[jira] Commented: (MRELEASE-6) Multiproject Release: No check in
[ http://jira.codehaus.org/browse/MRELEASE-6?page=comments#action_57636 ] Olivier Lamy commented on MRELEASE-6: - Personnaly, I named directory (module and scm) striclty equals (;-) ). In fact, I used something like this - root-module/pom.xml src/site/global documentation - api-module/pom.xml - root-module as this to edit it with eclipse. But it's easy to change to ./pom.xml (root) site-module with global documentation not a real trouble Thanks, Olivier > 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: > > ../hhla.library.pom > ../hhla.library.site > ../hhla.lang > ../hhla.common.log4jx > -- 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]
[jira] Commented: (MRELEASE-6) Multiproject Release: No check in
[ http://jira.codehaus.org/browse/MRELEASE-6?page=comments#action_57634 ] Kenney Westerhof commented on MRELEASE-6: - One more thing: only pom 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: > > ../hhla.library.pom > ../hhla.library.site > ../hhla.lang > ../hhla.common.log4jx > -- 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]
[jira] Commented: (MRELEASE-6) Multiproject Release: No check in
[ http://jira.codehaus.org/browse/MRELEASE-6?page=comments#action_57633 ] Kenney Westerhof commented on MRELEASE-6: - 1) that is best practise. But having a module directory 'a' containing a pom with artifactId 'b' should work though. 2) Correct, that is the default. When scanning for parent poms, first ../pom.xml is checked to see if it matches the tag. If that fails, the local/remote repositories are consulted for that pom. The problem here with the SCM module is that if your CVS/Subversion/Whatever repository layout does not match the default parent/module inheritance model (module = artifactId subdir, parent = ..), you have to specify the SCMUrl in every pom. Only when the default layout is used, Maven can make a well educated guess on the SCM url. The same goes for site urls, btw. In theory, maven should use the definitions to define SCM urls for child modules. But it poses some problems. Say you want to release a submodule. You do the release there. Maven will try to guess the SCM url by traversing the parent-tree until an SCM url is found (actually it'll go all the way up to the built-in root pom..). It first tries ../pom.xml, which does not exist. It then retrieves the pom from the repository. Since there's no relation between the module directory name and the artifactId, it cannot see which of the tags corresponds to the project you're currently trying to release. It can only append the current artifactId to that SCM url and hope it's correct. I hope this clarifies a lot. There is no easy solution.. > 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: > > ../hhla.library.pom > ../hhla.library.site > ../hhla.lang > ../hhla.common.log4jx > -- 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]
