You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Oran Kelly (JIRA)" <ji...@codehaus.org> on 2009/03/30 15:22:12 UTC
[jira] Commented: (MNG-2979) Cross module dependencies for
multi-module site
[ http://jira.codehaus.org/browse/MNG-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171392#action_171392 ]
Oran Kelly commented on MNG-2979:
---------------------------------
We also have a multi-module project of the form:
workspace/parent-module
workspace/module1
workspace/module2
...
If we start with a local repository that has none of these modules deployed and utter "mvn clean install site" in the parent-module, the build fails because it cannot resolve module1 as a dependency.
I have checked with the recently released 2.0.10 and 2.1.0 and the problem still exists in both.
> Cross module dependencies for multi-module site
> -----------------------------------------------
>
> Key: MNG-2979
> URL: http://jira.codehaus.org/browse/MNG-2979
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.0.5
> Environment: Linux 2.6.18-gentoo-r6 #2 SMP PREEMPT Wed Feb 28 10:25:50 CET 2007 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
> Reporter: Wally Wallou
> Priority: Minor
> Fix For: 2.1.x
>
> Attachments: gwttk-m2.zip, package.txt, site.txt
>
>
> Considering a multi-module project A which declares two sub-projects (modules) B and C. Having module C indicating in its POM a dependency against module B. Compilation and packaging work great without having to install module B in maven local repository, it locate module B for module C using declared aggregation at top level project A.
> But for site goals it does not work, that is to say when maven try to generate site for module C it tells that module B artifact cannot be found. So we have to install module B to be able to generate module C site, whereas it is not necessary for compile or package goals.
> I think it would be great if site goals behaves like compile and package with aggregation. It would be more coherent, and avoid to have to run install just for site goals.
--
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