[MNG-1797] Dependency excludes apply to every subsequent dependency, not just the one it is declared under.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.1
• Fix Version/s: 2.0.5
• Assignee: John Dennis Casey
• Reporter: David Hawkins
• Created: 09/Dec/05 15:00
• Updated: 05/Apr/15 22:08
• Resolved: 05/Sep/06 11:43

Description

If you specify ANY dependency excludes, all dependencies after that one in the pom will also exclude what you specified. They appear to be cumulative on every dependency in that they bleed over into sibling dependencies.
It's easy to test if you add an exclusion to a random dependency. This exclusion should exclude a required transitive dependency that is included by a dependency lower in the list. You will find that the dependency lower in the list no longer includes the required dependency because it is using the filter you declared in the other dependency.

Issue Links

• is duplicated by: MNG-1557 Dependency Ignored
• is duplicated by: MNG-2032 Bug in dependency exclusions processing (ArtifactFilter's)
• is duplicated by: MNG-2326 exclusion of transitive dependency is too dominant
• is duplicated by: MNG-2354 exclusion of a dependency prevents the dependency being added normally
• is duplicated by: MNG-2420 exclusion on dependency seems to act global on POM
• is related to: MANTTASKS-134 Exclusions in dependencies should not exclude a direct dependency
• is related to: MNG-1977 Global dependency exclusions
• relates to: MNG-4180 [regression] Dependency exclusions are applied globally