Inherit transitive dependencies with runtime scope

Details

  • Complexity:
    Intermediate

Description

Transitive dependencies of scope "compile" should be inherited with scope "runtime" only. This would avoid unwanted usage of 3rd party packages and make explicit dependencies visible. It should be possible at least to run Maven in such a mode.

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MNG-2205 "provided" scope dependencies must be transitive

  • Critical - Crashes, loss of data, severe memory leak.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Joerg Schaible added a comment -

Should have been assigned to the component "Dependencies" ...

Show
Joerg Schaible added a comment - Should have been assigned to the component "Dependencies" ...
Hide
Permalink
Joerg Schaible added a comment -

Should have been "Transitive dependencies of scope "compile" should be inherited with scope "runtime" only"

Show
Joerg Schaible added a comment - Should have been "Transitive dependencies of scope "compile" should be inherited with scope "runtime" only"
Hide
Permalink
Jason van Zyl added a comment -

Maybe this could be another enforcer rule? Brian?

Show
Jason van Zyl added a comment - Maybe this could be another enforcer rule? Brian?
Hide
Permalink
Sei Syvalta added a comment -

Please read my comment in MNG-2205 (don't wan't to copy-paste that here). Generally, I think this should be how maven would work, so transitive dependencies would not be included in compile time classpath.

I know some people will think otherwise, so perhaps providing an option would be good, but I would prefer the default being as Joerg suggests.

Could someone fix the subject?

Show
Sei Syvalta added a comment - Please read my comment in MNG-2205 (don't wan't to copy-paste that here). Generally, I think this should be how maven would work, so transitive dependencies would not be included in compile time classpath. I know some people will think otherwise, so perhaps providing an option would be good, but I would prefer the default being as Joerg suggests. Could someone fix the subject?
Hide
Permalink
Benjamin Bentmann added a comment -

Just as to clarify why the current behavior is as is: See the note on dependency scope on the Maven site. Seems to be a "better safe than sorry" approach.

Show
Benjamin Bentmann added a comment - Just as to clarify why the current behavior is as is: See the note on dependency scope on the Maven site. Seems to be a "better safe than sorry" approach.

People

  • Assignee:
    Unassigned
    Reporter:
    Joerg Schaible
Vote (9)
Watch (8)

Dates

  • Created:
    Updated: