[MNG-3420] In a reactor, attached artifacts with classifier should be used when generating classpath, instead of the whole output directory of the related project

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0.5, 2.0.6, 2.0.7, 2.0.8
• Component/s: Reactor and Workspace
• Flags: Patch
• Assignee: Brett Porter
• Reporter: Nicolas Rougé
• Created: 26/Feb/08 05:22
• Updated: 05/Apr/15 14:53
• Resolved: 26/Feb/09 05:01

Description

In a reactor, when a project depends on attached artifacts with classifier of other projects (such as jar assemblies), the generated classpath includes all the output directory of the related projects.
This can lead to problems for example if these attached artifacts contains only a subset of the output directory of the related project.

I attached an example that shows this problem :
1/ launch "mvn install" in the "test-classifier" directory (POM project basedir), you'll get a compilation failure for module3.
2/ launch "mvn install" in the "module3" directory, it works.

I also attached a patch (it affects only MavenProject class).

Issue Links

• duplicates: MNG-2720 Multiproject dependencies not accurate for project.compileClasspathElements when run from root project
• relates to: MNG-2871 Subartifact (ejb-client, test-jar etc.) are not reselved as active project artifacts in build phases prior to package