[MNG-5431] Support "include" scope

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.0.4, 3.2.x
• Component/s: Dependencies, Inheritance and Interpolation, POM
• Assignee: Unassigned
• Reporter: Matthew T. Adams
• Created: 05/Feb/13 08:37
• Updated: 27/Jun/14 14:42
• Resolved: 23/Jan/14 13:06

Description

I'd like to request an improvement over the current pom import support.

The current import support only goes so far as adding dependencies to the dependencyManagement section of a pom. The importing pom still is left to add those dependencies to its own dependencies, which is inconvenient, especially for imported poms that define many dependencies.

Instead, I propose the addition of a new scope called "include" that can be used to add the imported pom's <dependencies> section to the importing pom's <dependencies> section.

A pom that wants to "include" another pom, then, would simply declare the dependency on the included pom's groupId:artifactId:version, but use a scope of "include", which would imply type "pom". The important thing to realize is that this could be done in the <dependencies> section of the including pom (not necessarily <dependencyManagement><dependencies>). For example, in the including pom's dependencies (at XPath "project/dependencies", not "project/dependencyManagement/dependencies"):

<dependency>
<groupId>me.matthewadams</groupId>
<artifactId>datanucleus-rdbms</artifactId>
<scope>include</scope> <Unable to render embedded object: File (-- NEW) not found. different from "import"! -->
<version>3.1.4</version>
</dependency>

The scope "include" implies "<type>pom</type>"; declaring it explicitly would be ok, but declaring any other <type> would be an error.

See the two poms attached to this request for a more thorough example.

Also, see user list discussion at http://maven.40175.n5.nabble.com/New-Maven-idea-include-import-tp5745916.html