maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Sinesio (JIRA)" <>
Subject [jira] Commented: (MNG-2979) Cross module dependencies for multi-module site
Date Thu, 30 Apr 2009 03:18:45 GMT


Andy Sinesio commented on MNG-2979:

John, it looks like you didn't verify the problem properly.   Running "mvn install site" is
the workaround.

The actual issue is that running "mvn site" in a multi-module project fails because Maven
does not resolve dependencies properly.

> Cross module dependencies for multi-module site
> -----------------------------------------------
>                 Key: MNG-2979
>                 URL:
>             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,, 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:
For more information on JIRA, see:


View raw message