Batik PDF/SVG Export won't build with newer Java Version #97
Comments
Skgland
changed the title
|
Batik apparently fixed this in 1.11 and it appears this repo Vendors 1.7 |
|
It appears that 1.11 still contains a problematic dependency on xml-apis https://issues.apache.org/jira/browse/BATIK-1289 |
sailingKieler
added a commit
that referenced
this issue
Dec 22, 2022
…ctually required by our code, fixes #97 This avoids the 'The package org.w3c.dom is accessible from more than one module: <unnamed>, java.xml' error that is due to fact that classes of the 'org.w3c.dom' package are part of the JDK since Java9 (in module 'java.xml'), and also part of the packaged batik 1.7 distribution. At runtime classes of the JDK/JRE will take precedence (root class loader is asked first), so their counterparts in the provided jar won't be loaded.
sailingKieler
added a commit
that referenced
this issue
Jan 9, 2023
…ctually required by our code, fixes #97 This avoids the 'The package org.w3c.dom is accessible from more than one module: <unnamed>, java.xml' error that is due to fact that classes of the 'org.w3c.dom' package are part of the JDK since Java9 (in module 'java.xml'), and also part of the packaged batik 1.7 distribution. At runtime classes of the JDK/JRE will take precedence (root class loader is asked first), so their counterparts in the provided jar won't be loaded.
sailingKieler
added a commit
that referenced
this issue
Jan 9, 2023
…ctually required by our code, fixes #97 This avoids the 'The package org.w3c.dom is accessible from more than one module: <unnamed>, java.xml' error that is due to fact that classes of the 'org.w3c.dom' package are part of the JDK since Java9 (in module 'java.xml'), and also part of the packaged batik 1.7 distribution. At runtime classes of the JDK/JRE will take precedence (root class loader is asked first), so their counterparts in the provided jar won't be loaded.
sailingKieler
added a commit
that referenced
this issue
Jan 9, 2023
…ctually required by our code, fixes #97 This avoids the 'The package org.w3c.dom is accessible from more than one module: <unnamed>, java.xml' error that is due to fact that classes of the 'org.w3c.dom' package are part of the JDK since Java9 (in module 'java.xml'), and also part of the packaged batik 1.7 distribution. At runtime classes of the JDK/JRE will take precedence (root class loader is asked first), so their counterparts in the provided jar won't be loaded.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the newer Java (9+) Versions the module system was added and this disallows packages split over modules.
The problem is that the package
org.w3c.domis defined by the modulejava.xmlin the Standard Library and by the dependencieson the Classpath which contribute to the package.
This causes a build error as the package is defined in more than one module: and
java.xmlThe text was updated successfully, but these errors were encountered: