Le mar. 5 sept. 2023 à 14:12, Martin Desruisseaux < martin.desruisse...@geomatys.com> a écrit :
> 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. > Depends a bit the plugins but we have some shared configuration (my 2 cts being they often bother more than they help for tool based impl) but depends the stack the plugin relies on. A good example is that surefire will not depend on that today cause it does a ton of things around the launcher so not sure it would help to search there. Plugins are really callbacks for maven more than tool based runtimes. > > > > 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. > Not really, when your module is JPMS friendly and you have some JPMS transitive deps you can still desire to put them in the classpath (it is very common for libs) and run a surefire execution with JPMS "only". So whatever you do, JPMS is an user explicit configuration to dispatch between classpath and module path, the rare cases it works automatically (one way or the others) would fake a support a build tool can't guarantee by design. Indeed my preference is to stick to classpath by default since it is the most used runtime and enable the module-path to be tuned per plugin when needed, an auto injection with an extension is not hard to do but would be random in terms of coverage and actual runtime support (thinking to jib, assemblies etc which are the actual runtime after the build). Hope it makes sense. > > Martin > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
