[MNG-4608] Cross module dependencies for multi-module projects

• Type: Improvement
• Status: Closed
• Priority: Blocker
• Resolution: Duplicate
• Affects Version/s: 2.0.9
• Environment: windows, jdk1.6.0_16
• Assignee: Benjamin Bentmann
• Reporter: Robert Lieb
• Created: 26/Mar/10 04:07
• Updated: 26/Mar/10 06:32
• Resolved: 26/Mar/10 06:32

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.
Module B uses the shade plugin to 'merge' classes from B with his dependencies.
Separate install of B and C works fine, but an install on A fails by compiling C
because of missing classes. Maven don't use the generated jar file of B for compiling C.
I need a different behaviour (maybe command line option) to change it.

This is not only related to shade plugin. In any cases in which a maven project uses
some 'manipulation' plugins after compile phase, will fail.

Issue Links

• duplicates: MNG-2720 Multiproject dependencies not accurate for project.compileClasspathElements when run from root project