[MNG-4630] POMs that inherit from an aggregating POM should also inherit modules/reactors

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Component/s: Dependencies
• Assignee: Benjamin Bentmann
• Reporter: Emil Sit
• Created: 11/Apr/10 20:39
• Updated: 12/Apr/10 04:28
• Resolved: 12/Apr/10 04:28

Description

I have a simple use case where I use both inheritance and aggregation across several modules.

When I run "mvn -pl subproject2 -am package" in the top-level, there is no need to 'mvn install' for subproject1, because both subprojects are aggregated at the top-level and the build reactor knows to build subproject1 first and stick it in the classpath for subproject2. However, when I am in the subproject2 directory and run 'mvn package', the build reactor does not.

I don't know if this is a bug or by design, but it seems to me that through inheritance, subproject2's invocation should be aware of the other modules that it is being aggregated with and be able to calculate dependencies without requiring installation into the local repository.

Issue Links

• duplicates: MNG-4324 Add the ability to launch a reactor build with -amd or -am options from a submodule