[
http://jira.codehaus.org/browse/MNG-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4630.
----------------------------------
Resolution: Duplicate
Assignee: Benjamin Bentmann
> POMs that inherit from an aggregating POM should also inherit modules/reactors
> ------------------------------------------------------------------------------
>
> Key: MNG-4630
> URL: http://jira.codehaus.org/browse/MNG-4630
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Emil Sit
> Assignee: Benjamin Bentmann
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
