[
https://issues.apache.org/jira/browse/MJLINK-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610150#comment-16610150
]
Karl Heinz Marbaise commented on MJLINK-6:
------------------------------------------
If someone will help just start with making an test project which shows how it
works and document the steps how to get there...
> 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
> Priority: Minor
> Labels: up-for-grabs
>
> 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)
