[jira] Updated: (MNG-2979) Cross module dependencies for multi-module site

["John Casey (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MNG-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey updated MNG-2979:
----------------------------

    Attachment: build.log

I opened the gwttk-m2.zip file, cd'ed into the root directory, and executed the following:

{noformat}
mvn clean install site
{noformat}

using Maven 2.1.0 and JDK 1.4 on OS X 10.5, and had no problems. The attached build.log file reflects this. Note that I had made sure that all of net/asquare/** was removed from the local repository before doing so.

As for the approach of simply calling `mvn site` from the root without building at least to the package phase at the same time, where is the jar file for the dependency supposed to come from if nothing is producing it? I'm re-checking this process using `mvn clean package site` now, and will report my results.

> 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
>            Assignee: John Casey
>            Priority: Minor
>             Fix For: 2.2.x
>
>         Attachments: build.log, 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