-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Since the element represents the path where the jlink tool discovers observable modules, I thought I could specify the path of the jmod directory of a linux jdk when building under Windows, but it does not seem to have the desired effect: the target image contains the binaries of the Windows JDK.
This is how I have specified it:
<properties>
<maven.compiler.source>11</maven.compiler.source>
<maven.compiler.target>11</maven.compiler.target>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<jmods.dir>/Java/amazon-corretto-11.0.12.7.1-linux-x64/jmods</jmods.dir>
</properties>
<dirsets>
<dirset>
<directory>${jmods.dir}</directory>
<includes>
<include>**/*</include>
</includes>
</dirset>
</dirsets>
Is this functionality supported?
Metadata
Metadata
Assignees
Labels
No labels