[ 
http://jira.codehaus.org/browse/MNG-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183952#action_183952
 ] 

Ronald Kurr commented on MNG-2979:
----------------------------------

I just wanted to add that I'm seeing the same behaviour under Maven 2.2.0.  
Like Oran said, it does not appear to be fixed.  Maybe this ticket should be 
reopened?  

> 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.0
>
>         Attachments: build.log, gwttk-m2.zip, maven-core-2.0.11-SNAPSHOT.jar, 
> maven.diff, maven.diff, mng-2979-testcase.tar.gz, package.txt, site.txt, 
> to-package.log
>
>
> 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

        

Reply via email to