[MNG-4156] Local test scope shouldn't override transitive compile scope

• Type: Improvement
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.1.0
• Component/s: Dependencies
• Assignee: Unassigned
• Reporter: Stevo Slavić
• Created: 11/May/09 11:52
• Updated: 13/Oct/23 19:53

Description

Local test scoped dependencies shouldn't by default override compile scoped transitive dependencies. If one wanted to exclude transitive compile scoped dependency and have it available only in test scope, it would be more natural (for me at least) to require user to specify appropriate excludes section on a dependency that brought transitive dependency with it. In this case (local test scoped vs transitive compile scoped dependency), requiring user to explicitly specify excludes section would more clearly state/document the intention, while currently build tool silently makes a wrong decision (maybe there are times this decision is correct, but IMO it's correct in far less cases than it is wrong).

Attached is example project where current in most cases unwanted behavior can be reproduced.

Issue Links

• is duplicated by: MNG-6453 Local test scope shouldn't override transitive compile scope
• is related to: MNG-787 Dependency suggestion in current project should take precedence over transitive dependencies by default
• is superceded by: MNG-6453 Local test scope shouldn't override transitive compile scope
• relates to: MNG-6058 Test dependencies should override application dependencies only during testing
• relates to: MRESOLVER-391 Scope mediation improvements
• relates to: MNG-4789 [regression] Difference in compile scope dependency resolution