[MNG-2979] Cross module dependencies for multi-module site

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: 2.0.5
• Component/s: Artifacts and Repositories
• 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
• Assignee: John Dennis Casey
• Reporter: Wally Wallou
• Created: 04/May/07 09:02
• Updated: 30/Dec/09 21:27
• Resolved: 30/Dec/09 21:27

Description

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.