Le 2023-09-04 à 16 h 44, Romain Manni-Bucau a écrit :
I'd say open issues for the related plugins, several are known to be
used (not sure about javadoc but others should).
Is the class-path/module-path management duplicated by all modules? I do
not know Maven internal, but I though that it would be in some base
module shared by all plugins.
The cases where you don't use dependencies so means you can't really
use JPMS e2e so not sure it helps without new meta (properties).
New metadata are not needed when the Maven default behaviour is
suitable. It is the case for example if everything (the project and all
its dependencies, including transitive ones) are JPMS modules, in which
case there is no ambiguity and even today Maven works well. New metadata
are needed mostly for grey areas with partially modularized projects,
for testing or for advanced configuration. So while they are essential
in some cases (especially during transition to JPMS), they are not
mandatory in every cases.
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
