Le 2023-11-02 à 00 h 31, Tamás Cservenák a écrit :
Here is where I am currently:
https://cwiki.apache.org/confluence/display/MAVEN/Experiment+-+Explicit+JPMS+support
It seems that I cannot add comment on that page, so below are my proposals:
1) Modify the explanation of the "jar" type. It currently said "same as
today, added to classpath". It should be "same as today, automatic
dispatching". The automatic dispatching may be based on the current
heuristic rules (for compatibility reasons), or on new rules specified
by a global configuration option, or on what the library producers
declare (e.g. <packaging>module</packaging> in the POM of the
dependencies?).
2) Add a new "classes" type with explanation "a non-JPMS artifact, added
to class-path".
3) Add a column (or the information somewhere else) about mutually
exclusive types. For example "jar", "classes" and "module" types are
mutually exclusive.
4) Maybe omit "fatmodule" for now? That one may be difficult to do,
because it would require to merge all module-info files in a single one.
Even if we do so, the result will not be equivalent. In a JPMS world,
there are other tools (jmod, jimage, jlink…) that we may want to explore
before falling back on fatmodule.
Thanks,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
