Eclipse Build Error: Locating XML Classes After JDK 10 Upgrade
Several users have encountered a perplexing issue after switching the Java Build Path for their Maven project to JDK 10. Eclipse builds fail to locate classes related to XML processing, such as javax.xml.xpath.XPath and org.w3c.dom.Document. Intriguingly, a Maven build from Eclipse runs without errors.
Root Cause: Module Conflict
The root cause of this issue lies in the project's lack of a module-info.java file. Without this file, the project resides in the "unnamed module" and reads all observable named and unnamed modules, including "java.xml" from the JRE and "xml.apis" from the project's own classpath.
Unique Visibility Requirement
This situation violates the Java Language Specification's "unique visibility" requirement. Every qualified type name must have a uniquely visible package. However, the conflict arises because both "java.xml" and "xml.apis" contribute packages with the same names (e.g., java.xml.xpath).
Potential Solutions
To resolve this issue, consider the following solutions:
1. Add a module-info.java File
This file allows you to control which modules the project reads. By specifying requires java.xml; or requires xml.apis;, you can explicitly define the dependency relationships and avoid the conflict.
2. Avoid the Conflict in Eclipse
Without adding a module-info.java file, you can still prevent the conflict in Eclipse by using the "Modularity Details" dialog. Move all modules except for java.base to the left ("Available modules"), and re-add any necessary modules selectively.
Despite these solutions, the Eclipse error message remains inaccurate, failing to pinpoint the actual problem. Improvements have been made to the message, but the underlying issue persists.
The above is the detailed content of Why Does My Eclipse Maven Project Fail to Locate XML Classes After Upgrading to JDK 10?. For more information, please follow other related articles on the PHP Chinese website!