Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.0-alpha-3
-
Fix Version/s: 3.0-alpha-3
-
Component/s: Artifacts and Repositories
-
Labels:None
-
Complexity:Intermediate
Description
Scenario:
<dependencies> <dependency> <groupId>org.apache.maven.its.mng4180</groupId> <artifactId>a</artifactId> <version>0.1</version> <exclusions> <exclusion> <groupId>org.apache.maven.its.mng4180</groupId> <artifactId>b</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.apache.maven.its.mng4180</groupId> <artifactId>c</artifactId> <version>0.1</version> </dependency> </dependencies>
If b is a transitive dependency of c, the exclusion defined in a will also affect c, i.e. the class path would miss b although it's not excluded on c.
Issue Links
- is related to
-
MNG-1797
Dependency excludes apply to every subsequent dependency, not just the one it is declared under.
-
Fixed in r784296.