desruisseaux commented on PR #12745:
URL: https://github.com/apache/maven/pull/12745#issuecomment-5313947552

   I still do not understand what is the goal here. A `compile` scope *needs* 
to be transitive, even if the library does not expose this dependency in its 
API, because the library needs the dependency for its internal working. If the 
reason for making a dependency non-transitive is that the dependency is 
expected to be already present on the target platform, then this is the 
`provided` scope. If the reason is that the dependency is optional, then there 
is an `<optional>true</optional>` element for that. If the goal is to prevent 
users to `import` classes from the non-transitive dependency without explicit 
`<dependency>` declaration by the users, then this is already managed by the 
Java Module system.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to