[MNG-249] compile and package should be reactor-aware

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.0-beta-1
• Component/s: Plugins and Lifecycle
• Environment: any
• Assignee: Brett Porter
• Reporter: Kenney Westerhof
• Created: 05/Apr/05 11:11
• Updated: 07/Aug/10 12:48
• Resolved: 28/Jul/05 09:18

Description

When compiling or packaging a project consisting of subprojects
where one depends on another, maven should first check the build environment
for existing jars or classes (in target/ directories) from the dependent subproject,
rather than always looking in the local and remote repositories for jar artifacts.

Attached is a very simple test-case with 2 subprojects, where one depends
on the other.

Only m2 install works; m2 compile and m2 package should also work.

Issue Links

• relates to: MNG-2921 ejb-client dependency no longer resolved in reactor build
• relates to: MNG-1088 Plugins built and used within the same multiproject build fail unless lifecycle phase is compile or later
• relates to: MNG-3043 Allow 'mvn test' to work with test-jar dependencies in a reactor
• relates to: MNG-870 Make plugin discovery reactor aware