Hello Romain
Le 2023-12-19 à 18 h 07, Romain Manni-Bucau a écrit :
I fully understand that but my point - same as last time - is that
"modular-jar" does not give you the information you want, ie
"classpath for compiler, module for javadoc, resolved for tests" for
example.
As Tamas said, I don't think that developers would want to do that in
normal scenario. I believe that they will want the same configuration
applied consistently in all tools. To demonstrate my point, I plan to
test Maven 4 on Apache Spatial Information System (SIS), which is
already strongly JPMS-oriented. Actually, I had to move from Maven 3 to
Gradle because full JPMS support was not possible in Maven 3. My plan is
to test if I can move back to Maven 4 after JPMS support is completed.
My experience so far is that, in most cases, we really need the same
configuration applied everywhere: javac on main code, javac on test code
(with their --patch-modules options), java for running JUnit tests
(which need the exact same set of --patch-modules than the one used for
compiling the tests), javadoc, etc. Everywhere, the configuration really
needs to be the same.
I have no doubt that some developers will need to hack the system for
some special needs. We can try to offer that possibility as much as we
can. But I believe that the default should be: apply user's wishes
consistently in all plugins, and allow override when really needed.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
