[
https://issues.apache.org/jira/browse/BATIK-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043953#comment-18043953
]
Samael Bate commented on BATIK-1289:
------------------------------------
There's a similar issue in [https://github.com/apache/xerces-j/], there's been
some traction recently getting changes but a new release will need to be
published to maven central.
It's really annoying that xml-apis bundles classes that are already in the JDK.
See https://issues.apache.org/jira/browse/XMLCOMMONS-101 the sources for
{{xml-apis-ext}} have been moved to a branch of xerces-j
> batik, xml-apis-ext and java modules
> ------------------------------------
>
> Key: BATIK-1289
> URL: https://issues.apache.org/jira/browse/BATIK-1289
> Project: Batik
> Issue Type: Bug
> Affects Versions: 1.12
> Reporter: Tore Halset
> Priority: Major
>
> batik uses xml-apis-ext that include org.w3c-packages, but there are also
> some org.w3c-packages in java core modules.
>
> Typical error in Eclipse is The package org.w3c.dom is accessible from more
> than one module: {{<unnamed>}}, org.w3c.
>
>
>
> I have a workaround for this in my project now, but hope for a better more
> official solution.
> # Moved all of the org.w3c from xml-apis-ext to packages not used by other
> modules. [https://github.com/halset/xml-apis-ext]
> # Refactored batik to use the new package names.
> [https://github.com/halset/xmlgraphics-batik/tree/modulefix]
>
>
> Do others have the same issue or am I doing something wrong?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
