[
https://issues.apache.org/jira/browse/MJLINK-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MJLINK-6.
-------------------------------
Resolution: Fixed
Assignee: Robert Scholte
Fix Version/s: 3.0.0
Fixed in
[f51f117d08a3f84072c85bb60d496a99227597cb|https://gitbox.apache.org/repos/asf?p=maven-jlink-plugin.git;a=commit;h=f51f117d08a3f84072c85bb60d496a99227597cb]
Thanks for the patch!
> Allow set the jmods path
> ------------------------
>
> Key: MJLINK-6
> URL: https://issues.apache.org/jira/browse/MJLINK-6
> Project: Maven JLink Plugin
> Issue Type: Improvement
> Affects Versions: 3.0.0-alpha-2
> Reporter: Roberto Araujo
> Assignee: Robert Scholte
> Priority: Minor
> Labels: up-for-grabs
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The current version of the plugin hard-coded the `jmods` folder (based on
> `jlink` binary location). But, for instance, if I want to build a runtime
> image for Linux running the build in a OSX the runtime image will not be
> compatible.
> I suggest to allow users define the JDK `jmods` folder, and if nothing is
> set, use the one based on the JAVA_HOME/Toolchain configuration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
