Eclipse can’t find XML related classes after switching build path to JDK 10

by

I assume that the project being migrated from Java 1.8 still has no module-info.java. This implies you are compiling code in the “unnamed module”.

Code in the unnamed module “reads” all observable named and unnamed modules, in particular it reads module “java.xml” from the JRE System Library. This module exports package like java.xml.xpath.

Additionally, you have xml-apis.java on the classpath, which contributes another set of packages of the same names (java.xml.xpath and friends). These are said to be associated to the unnamed module, like your own code.

This situation violates the requirement of “unique visibility” as defined in JLS §7.4.3 (last paragraph). In particular every qualified type name Q.Id (JSL §6.5.5.2) requires that its prefix Q is a uniquely visible package (I’m disregarding the case of nested types for simplicity). Ergo: the program is illegal and must be rejected by compilers.

This leaves us with one question and two solutions:

(1) Question: Why is javac accepting the program?

(2) Solution: If you add module-info.java to your project, you can control via requires which module your project reads, either requires java.xml; or requires xml.apis; (where “xml.apis” is the automatic module name of “xml-apis-1.4.01.jar).

(3) Solution: Short of turning your project into a module, you can still avoid the conflict by excluding java.xml from the set of observable modules. On the command line this would be done using --limit-modules. The equivalent in Eclipse is the “Modularity Details” dialog, see also the JDT 4.8 New&Noteworthy (look for Contents tab). Since java.xml is implicitly required via a lot of other default-observable modules, it may be a good idea to push everything except for java.base from right (“Explicitly included modules”) to left (“Available modules”) (and selectively re-add those modules that your project needs).

PS: Eclipse still doesn’t provide an ideal error message, instead of “cannot be resolved” it should actually say: “The package javax.xml.xpath is accessible from more than one module: javax.xml, <unnamed>.

PPS: Also weird: how come that changing the order between JRE and a jar on the classpath (such ordering is not a concept supported by javac nor JEP 261) changes the behavior of the compiler.

EDITs:

  • Alex Buckley confirmed that the given situation is illegal, despite what javac says. Bug against javac has been raised as JDK-8215739. This bug has been acknowledged months before the release of Java 12. As of 2019-06 it has been decided that also Java 13 will ship without a fix. Similarly for Java 14. The bug was temporarily scheduled for Java 15, but this plan has been dropped on 2020-04-20.
  • Eclipse error message has been improved to mention the real problem.
  • In Eclipse 2019-06 the UI used for Solution (3) has been revamped. Up-to-date documentation can be found in the online help.

More Related Contents:

  1. No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?
  2. Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.5 or one of its dependencies could not be resolved
  3. Unable to compile simple Java 10 / Java 11 project with Maven
  4. How do I add a Maven dependency in Eclipse?
  5. Create a Maven project in Eclipse complains “Could not resolve archetype” [duplicate]
  6. How to resolve Unable to load authentication plugin ‘caching_sha2_password’ issue
  7. Cannot change version of project facet Dynamic Web Module to 3.0?
  8. Lombok is not generating getter and setter
  9. What does Maven Update Project do in Eclipse?
  10. java.lang.ClassNotFoundException: org.apache.struts2.dispatcher.ng.filter.StrutsPrepareAndExecuteFilter when starting Simple Struts2 Application
  11. java.lang.NoClassDefFoundError: org/springframework/core/env/ConfigurableEnvironment
  12. Maven “build path specifies execution environment J2SE-1.5”, even though I changed it to 1.7
  13. Using Eclipse Java Compiler (ecj) in maven builds
  14. Maven Java Version Configuration ignored by Eclipse/Idea
  15. Maven dependencies not visible in WEB-INF/lib
  16. jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
  17. Unable to complete the scan for annotations for web application [/app] due to a StackOverflowError
  18. Display omitted versions in maven dependency:tree?
  19. Maven 3.3.1 ECLIPSE: -Dmaven.multiModuleProjectDirectory system propery is not set
  20. How to solve maven 2.6 resource plugin dependency?
  21. Maven build failed: “Unable to locate the Javac Compiler in: jre or jdk issue”
  22. Cannot load properties file from resources directory
  23. JavaFX Maven Plug-in: No plugin found for prefix ‘jfx’ in the current project and in the plugin groups
  24. How do I enable index downloads in Eclipse for Maven dependency search? [duplicate]
  25. get rid of POM not found warning for org.eclipse.m2e:lifecycle-mapping
  26. How to build and run Maven projects after importing into Eclipse IDE
  27. ClassNotFoundException DispatcherServlet when launching Tomcat (Maven dependencies not copied to wtpwebapps)
  28. How to set environment variables to an application on OSX Mountain Lion?
  29. maven missing dependency jta-1.0.1b
  30. Proper fix for Java 10 complaining about illegal reflection access by jaxb-impl 2.3.0?

Leave a Comment