[MNG-6058] Test dependencies should override application dependencies only during testing

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 4.0.0
• Assignee: Unassigned
• Reporter: Christian Schulte
• Created: 07/Jul/16 00:01
• Updated: 22/Oct/24 19:54

Description

The following graph

POM
|->a 2.0 compile
|-->b 2.0 compile
|->b 1.0 test

will be mediated to

POM
|->a 2.0 compile
|->b 1.0 test

The test dependency on b will make the transitive application dependency on b disappear. Maven should understand that the application dependency on b in version 2.0 is part of the application classpath and that the test dependency on b in version 1.0 is part of the test classpath only (overriding the application classpath). If someone adds a dependency on a project like that, the test dependency will disappear because the test scope is not transitive so that a "consuming" project gets a different application classpath than the project itself.

Issue Links

• causes: MDEP-812 Error opening zip file or JAR manifest missing : ${groupId:artifactId:jar}
• causes: MDEP-791 Non-test scoped and transitive dependencies in compile scope
• is blocked by: MNG-6056 Implement Feature Toggle Module to handle Feature Toggles
• is related to: MNG-6224 Dependency version from test scope leaks into compile scope
• is related to: MNG-7852 Use all the versions for dependency resolution rather than "nearest first" or "declared first"
• is related to: MNG-4156 Local test scope shouldn't override transitive compile scope
• relates to: MRESOLVER-391 Scope mediation improvements
• relates to: MDEP-791 Non-test scoped and transitive dependencies in compile scope
• supercedes: MNG-5988 Dependency mediation should prioritize transitive dependencies based on scope.