
| Key: |
MNG-2315
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
Carlos Sanchez
|
| Votes: |
87
|
| Watchers: |
55
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Duplicate
|
|
|
|
This issue is duplicated by:
|
|
MNG-2435
Switch for turning off transitive dependencies
|
|
|
|
|
Related
|
|
This issue relates to:
|
|
|
MNG-3832 Allow wildcards in dependency exclusions
|
|
|
|
|
|
|
|
Something like
<dependency>
...
<excludeTransitive>true</excludeTransitive>
</dependency>
|
|
Description
|
Something like
<dependency>
...
<excludeTransitive>true</excludeTransitive>
</dependency> |
Show » |
Sort Order:
|
Maven2 is all about dependency management, and transient dependencies are an important part of it. Giving a switch to exclude all the transient dependencies would be an cogent thing to do.
Having been able to obtain transient dependencies is an powerful feature. With the scenarios we have encountered so far, it has been obvious that a some sort of control over transient dependency is a viable solution.
If we could restrict that, Maven2 should look for particular depth in the transient tree, rather than all the way down, it would be a much more valuable thing for the users.
Thus,
<dependency>
...
<transientDepth>1</transientDepth>
</dependency>
Thus, EII transientDepth would contain the depth that the transient resolution framework should look in the transient dependent tree. Value of 1 mean, dependencies in the next level only.
if transientDepth is 0, it is same as <excludeTransitive>true</excludeTransitive>.
We know Maven2 rocks and has addressed many of the building issues. Hope we would get a way to control the transient dependencies as well. (What about 2.0.8
)