[BATIK-1249] [PATCH] batik sub jars does not adhere to the java 11 module system

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Assignee: Simon Steiner
• Reporter: Thomas Pasch
• Created: 28/Dec/18 15:53
• Updated: 16/Jan/19 07:14
• Resolved: 15/Jan/19 13:42

Description

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.

Issue Links

• links to: GitHub Pull Request #17