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 "simon steiner (JIRA)" <ji...@apache.org> on 2019/01/15 11:25:00 UTC
[jira] [Updated] (BATIK-1249) [PATCH] batik sub jars does not
adhere to the java 11 module system
[ https://issues.apache.org/jira/browse/BATIK-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
simon steiner updated BATIK-1249:
---------------------------------
Summary: [PATCH] batik sub jars does not adhere to the java 11 module system (was: batik sub jars does not adhere to the java 11 module system)
> [PATCH] batik sub jars does not adhere to the java 11 module system
> -------------------------------------------------------------------
>
> Key: BATIK-1249
> URL: https://issues.apache.org/jira/browse/BATIK-1249
> Project: Batik
> Issue Type: Bug
> Reporter: Thomas Pasch
> Priority: Major
>
> If you use the batik sub jars (i.e. all batik jars except batik-all) with java 11 you will get the following compile error:
> ```
> error: the unnamed module reads package org.w3c.dom.events from both java.xml and batik.ext
> error: the unnamed module reads package org.apache.batik.util from both batik.util and batik.constants
> ```
> This is because the jars share some (java class) code in the {{same}} packages.
> The new java 11 (or java 9) module system does not like this kind of 'split jars'. The agreed-upon long-term solution to split jars is to separate the package namespaces.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org