desruisseaux commented on PR #12745: URL: https://github.com/apache/maven/pull/12745#issuecomment-5314836979
> JPMS was introduced in Java 9 nearly a decade ago, yet adoption remains surprisingly low across the broader ecosystem I believe that the low adoption is because using Java Module in Maven 3 and Gradle is very hard, especially when we need to deal with the `--add-exports` options for running the tests. Making Java Modules easy to use, as we are trying to do in Maven 4, may be a game changer. We could enforce the requirement that `compile` scope can be used only with `requires` module statements, and that as soon as there is at least one `requires transitive` statement the scope must be `api`. But in the context of Java modules, the benefit of distinguishing those two scopes at the `pom.xml` level is not obvious. In the context of classpath applications, there is indeed a benefit. But saying to developers "if you want that benefit, you need to migrate to Java modules" could also be a strategy for encouraging that transition, provided that we made it easy. -- 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]
