-
Notifications
You must be signed in to change notification settings - Fork 578
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
spotbugsTestCases is not compilable anymore in Eclipse #1316
Labels
Comments
OK, looks like the problem is coming from the spotbugs dependency on See https://www.mhonarc.org/archive/html/xsl-list/2019-04/msg00020.html |
iloveeclipse
added a commit
that referenced
this issue
Sep 29, 2020
This fixes issue #1316 and finally fixes issue #1315. This change switches from Jaxen 1.1.6 to 1.2.0 to allow compilation of the projects that rely on SpotBugs project with Java 11. Jaxen is a transitive optional dependency of dom4j that we use in SpotBugs. Jaxen 1.1.6 ships org.w3c.dom package, which is also now shipped by JDK in java.xml module. Java 9+ comiler disallow compilation if modules on module path ship same package. So compilation of spotbugsTestCases with Java 11 fails if the target release is 11 with the error: "The package org.w3c.dom is accessible from more than one module: <unnamed>, java.xml". Solution is to update Jaxen to 1.2.0 version, that does not ship org.w3c.dom package anymore. Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
iloveeclipse
added a commit
that referenced
this issue
Sep 29, 2020
This fixes issue #1316 and finally fixes issue #1315. This change switches from Jaxen 1.1.6 to 1.2.0 to allow compilation of the projects that rely on SpotBugs project with Java 11. Jaxen is a transitive optional dependency of dom4j that we use in SpotBugs. Jaxen 1.1.6 ships org.w3c.dom package, which is also now shipped by JDK in java.xml module. Java 9+ comiler disallow compilation if modules on module path ship same package. So compilation of spotbugsTestCases with Java 11 fails if the target release is 11 with the error: "The package org.w3c.dom is accessible from more than one module: <unnamed>, java.xml". Solution is to update Jaxen to 1.2.0 version, that does not ship org.w3c.dom package anymore. Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
1 task
iloveeclipse
added a commit
that referenced
this issue
Sep 29, 2020
This fixes issue #1316 and finally fixes issue #1315. This change switches from Jaxen 1.1.6 to 1.2.0 to allow compilation of the projects that rely on SpotBugs project with Java 11. Jaxen is a transitive optional dependency of dom4j that we use in SpotBugs. Jaxen 1.1.6 ships org.w3c.dom package, which is also now shipped by JDK in java.xml module. Java 9+ comiler disallow compilation if modules on module path ship same package. So compilation of spotbugsTestCases with Java 11 fails if the target release is 11 with the error: "The package org.w3c.dom is accessible from more than one module: <unnamed>, java.xml". Solution is to update Jaxen to 1.2.0 version, that does not ship org.w3c.dom package anymore. Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
iloveeclipse
added a commit
that referenced
this issue
Oct 6, 2020
This fixes issue #1316 and finally fixes issue #1315. This change switches from Jaxen 1.1.6 to 1.2.0 to allow compilation of the projects that rely on SpotBugs project with Java 11. Jaxen is a transitive optional dependency of dom4j that we use in SpotBugs. Jaxen 1.1.6 ships org.w3c.dom package, which is also now shipped by JDK in java.xml module. Java 9+ comiler disallow compilation if modules on module path ship same package. So compilation of spotbugsTestCases with Java 11 fails if the target release is 11 with the error: "The package org.w3c.dom is accessible from more than one module: <unnamed>, java.xml". Solution is to update Jaxen to 1.2.0 version, that does not ship org.w3c.dom package anymore. Signed-off-by: Andrey Loskutov <loskutov@gmx.de>
This was referenced Mar 8, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
spotbugsTestCases project is not compilable anymore in Eclipse, because of Java 11 "modules" crap that doesn't allow to compile Java 11 code if the modulepath contain two "modules" that ship same package. In current case we have Java 11 SDK that has
org.w3c.dom
declared injava.xml
package, and some other dependency:If I manually disable two dependencies below from .classpath, "accessible from more than one module" errors disappear:
I have to grock who and how brings which dependency to the module path that has
org.w3c.dom
included.The text was updated successfully, but these errors were encountered: