You are viewing a plain text version of this content. The canonical link for it is here.

Posted to batik-dev@xmlgraphics.apache.org by "Samael Bate (Jira)" <ji...@apache.org> on 2024/01/01 16:50:00 UTC

[jira] [Commented] (BATIK-1362) Add JPMS support

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

Samael Bate commented on BATIK-1362:
------------------------------------

Could someone please indicate if adding Automatic-Module-Name to the manifest is likely to be accepted. I don't mind making another PR for doing the multi release jar approach. Or perhaps targeting JDK 11 and above? Getting some movement in any of these directions would be good. JPMS is not going away

> Add JPMS support
> ----------------
>
>                 Key: BATIK-1362
>                 URL: https://issues.apache.org/jira/browse/BATIK-1362
>             Project: Batik
>          Issue Type: Improvement
>            Reporter: Samael Bate
>            Priority: Major
>              Labels: jpms, modules
>
> There are three potential options for supporting JPMS:
>  # Target a JDK above 8 and have module-info.java in each package
>  # Publish multi-release jars using latest maven-compiler-plugin with a module-info.java in src/main/java9/module-info.java
>  # Add Automatic-Module-Name to manifest of published jars



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org