maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roberto Araujo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MJLINK-6) Allow set the jmods path
Date Fri, 24 Nov 2017 16:23:00 GMT

    [ https://issues.apache.org/jira/browse/MJLINK-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16265399#comment-16265399
] 

Roberto Araujo commented on MJLINK-6:
-------------------------------------

But I can build a runtime image for Linux on OS X (At least for a docker containers). E.g.,
If I use the `--module-path` option the `jmod` folder from the Linux distribution (available
at http://jdk.java.net/9/) the assembled runtime image will work on Docker container (tested
with debian:sid). But if I use the `jmod` folder from my JAVA_HOME (i'm on OS X) the assembled
runtime image will not work in the container (the binaries are not compatible).

> 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
>
> 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
(v6.4.14#64029)

Mime
View raw message