You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Mukul Gandhi (Jira)" <xe...@xml.apache.org> on 2023/11/10 01:25:00 UTC
[jira] [Commented] (XERCESJ-1760) Splitpackage not allowed on modulepath
[ https://issues.apache.org/jira/browse/XERCESJ-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784643#comment-17784643 ]
Mukul Gandhi commented on XERCESJ-1760:
---------------------------------------
Few thoughts on this topic.
I guess, XercesJ team currently doesn't have a development goal to provide a future release that is natively aware of Java's module system. But for e.g, if XercesJ might support Java's module system, that we need to support Java 9 as a min Java version (because Java's module system was introduced with Java 9).
XercesJ currently supports Java 1.7 as min Java version. I feel that, XercesJ should support Java 1.8 as min Java version (but, many people from Java community consider that as well, an old enough Java version. But Java 1.8 I feel, is the best min version that is currently used by Java development community). But XercesJ to support Java 1.8 as min Java version has little challenges. XercesJ's XML Schema 1.1 validator, uses an XPath 2.0 processor (that's currently owned by Eclipse foundation's Web Tools Platform[WTP] project. But XercesJ uses a fork of that, which is hosted on github and managed by XercesJ team) that is built with Java 1.7. We should try to build that XPath 2.0 processor, with Java 1.8 (my last effort, to run that XPath 2.0 processor's test suite with Java 1.8 was not successful, due to that XPath 2.0 processors various dependencies on an old version of Eclipse IDE [from dated 2012 I guess]).
Another suggestion is that, you may use the XercesJ src code (XercesJ is open source) from svn repos, and can modify and build that only for your or your project's use the way you want.
I think that, this jira issue should not be classified as bug (but say, classified as a wish) and it should also not be a blocker.
> Splitpackage not allowed on modulepath
> --------------------------------------
>
> Key: XERCESJ-1760
> URL: https://issues.apache.org/jira/browse/XERCESJ-1760
> Project: Xerces2-J
> Issue Type: Bug
> Components: DOM (HTML)
> Affects Versions: 2.12.2
> Reporter: Kai Hofmann
> Priority: Blocker
>
> I am working with Java 17 completly based on the module path - so unit tests also there - also using cucumber. When using
> <dependency>
> <groupId>xerces</groupId>
> <artifactId>xercesImpl</artifactId>
> <version>2.12.2</version>
> </dependency>
> I got the following error message:
> Corrupted channel by directly writing to native stream in forked JVM 1.
> Stream 'java.lang.module.ResolutionException:
> Modules jdk.xml.dom and xercesImpl export package org.w3c.dom.html to module io.cucumber.cucumberexpressions'.
>
> Which ist a correct error, because on the modulepath split-packages are not allowed!
> Within the xercesImpl-2.12.2.jar you export the package org.w3c.dom.html which part of the jdk.xml.dom. And so this is a splitpackage.
>
> So please fix that to make xerces2-j working with the java module system.
>
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org