You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Marwell (Jira)" <ji...@apache.org> on 2023/01/08 18:55:00 UTC
[jira] [Commented] (MJLINK-65) Filter out automatic modules
[ https://issues.apache.org/jira/browse/MJLINK-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17655825#comment-17655825 ]
Benjamin Marwell commented on MJLINK-65:
----------------------------------------
Hi [~hg@apteryx.fr] - sorry for only replying now.
* Can you give us more details what you mean by "filtering out"? Whhaht is the expected jlink(.exe) call?
* Could other projects break?
* Did you consider or try to use optional/provided dependencies?
> Filter out automatic modules
> ----------------------------
>
> Key: MJLINK-65
> URL: https://issues.apache.org/jira/browse/MJLINK-65
> Project: Maven JLink Plugin
> Issue Type: New Feature
> Affects Versions: 3.1.0
> Reporter: Hervé Guillemet
> Priority: Major
>
> The plugin currently adds to the jlink image all modules found in the Maven dependencies. If such modules are automatic modules, jlink will fail.
> This prevents, for instance, to build the image of an application using JavaFX jars since JavaFX uses an empty automatic module (e.g. in javafx-controls-17.0.2.jar) as a dependency bridge between applications and platform specific jars (e.g. javafx-controls-17.0.2-linux.jar).
> Could you consider filtering out automatic modules ?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)