Le 28/08/2023 à 14:24, Martin Desruisseaux a écrit :
Rational: a direct dependency may be known to be compatible with both
the class-path and module-path (e.g. it may duplicate "module-info"
into "META-INF/services/"), but maybe some transitive dependencies are
not.
Another argument for making it non-transitive: while I'm currently
focusing on class-path versus module-path issue, I envision more
JPMS-related extensions to the POM model. For example <dependency> could
also contain an element telling to Maven "please emit --add-exports
arguments with me as the target for all non-exported packages of the
project". That would be useful for testing with JUnit or TestNG in
particular. But a project exporting all its packages to JUnit may not
want to export those packages to all JUnit dependencies as well. If
nevertheless a JUnit transitive dependency needs those exports, the
overriding mechanism suggested in previous email would work.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
