You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Apache Maven JLink Plugin, by default, add to the runtime (--add-modules option of jlink) all the modules of the Maven dependencies. This is particularly useful when the list of needed modules cannot be hard-coded using module descriptors (requires in module-info) but computed at build time by Maven.
Could you think of a way to add this feature ? Like allowing in <addmodules> the <dependencysets> element that can already be specified in <modulepath>.
Note that we already can write something like <addmodule>ALL-MODULE-PATH</addmodule> which works but has the side effect of including in the image all the modules from the JDK, not the sufficient modules.
The text was updated successfully, but these errors were encountered:
The Apache Maven JLink Plugin, by default, add to the runtime (
--add-modules
option of jlink) all the modules of the Maven dependencies. This is particularly useful when the list of needed modules cannot be hard-coded using module descriptors (requires
in module-info) but computed at build time by Maven.Could you think of a way to add this feature ? Like allowing in
<addmodules>
the<dependencysets>
element that can already be specified in<modulepath>
.Note that we already can write something like
<addmodule>ALL-MODULE-PATH</addmodule>
which works but has the side effect of including in the image all the modules from the JDK, not the sufficient modules.The text was updated successfully, but these errors were encountered: