-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to jaxen 1.2.0 #186
Comments
Simeon, do you want to take the lead on a release? Rolf had been doing it but he's gone silent (not sure why, hoping for the best). |
I've consulted my team, we'll try to separate the Our hands are unfortunately full already, we cannot devote time to preparing a |
And, I have resurfaced. Apologies, I was inadvertently sending all my JDOM correspondence in to an unmonitored mail folder.... This issue will take some finangling to get the builds through. There's a fair backlog I need to address, this will be part of it. |
Thanks! |
My team is in the process of updating an Eclipse-based product to compile with Java 11. Among other problems, we run into split package problems with
jdom 2.0.4
:[javac] The package org.w3c.dom is accessible from more than one module: <unnamed>, java.xml
This seems to be due to version of
jaxen
used in thejdom
bundle; thejaxen
version has the classorg.w3c.dom.UserDataHandler
, causing the compile error. We would like to avoid use of--limit-modules
and compile cleanly; we checked the latest availablejdom 2.0.6
but it containsjaxen 1.1.6
(up fromjaxen 1.1.4
in our case). Unfortunately thisjaxen
version still contains aorg.w3c.dom
package.jaxen 1.2.0
on the other hand does not. So it would be great if ajdom
bundle is available withjaxen 1.2.0
, to support applications that compile against JDK 9+.The text was updated successfully, but these errors were encountered: