[ https://issues.apache.org/jira/browse/XERCESJ-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17484581#comment-17484581 ]
Grzegorz Borkowski commented on XERCESJ-1689: --------------------------------------------- We're also getting Eclipse errors because org.w3c.dom.html.HTMLDOMImplementation is visible twice on the classpath now (one from xerces jar, one from java). I think it's generally a bad idea to include the classes from completely different package (org.w3c) into the org.apache java. Given the fact 99.99% of world is on java >= 1.4 now, the "normal" xerces release should not include HTMLDOMImplementation - if you still need to provide a special package for these miserables stuck with java 1.3, then maybe have a special branch and special package for them, called "xercesImpl-java13"? This would be more logical than other way round > Remove org.w3c.dom.html.HTMLDOMImplementation from xercesImpl.jar > ----------------------------------------------------------------- > > Key: XERCESJ-1689 > URL: https://issues.apache.org/jira/browse/XERCESJ-1689 > Project: Xerces2-J > Issue Type: Wish > Components: DOM (HTML) > Affects Versions: 2.11.0 > Reporter: Otmar Humbel > Priority: Critical > Fix For: 2.12.0 > > > The interface {{org.w3c.dom.html.HTMLDOMImplementation}} is part of the JDK > since Java {{1.7}}. > Java 1.7 has been EOL 'ed since a long time. > Is there any reason to keep this interface in {{xercesImpl.jar}}? It > produces a split package: > {{xerces-2_11_0: jdeps --jdk-internals -cp ./xercesImpl.jar}} > {{split package: org.w3c.dom.html [jrt:/jdk.xml.dom, ./xercesImpl.jar]}} > which prevents people from using modules in Java {{>= 9}}. -- This message was sent by Atlassian Jira (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org For additional commands, e-mail: j-dev-h...@xerces.apache.org