This compilation unit is not on the build path of a java project solution
When the project is imported into STS (eclipse based), there is a problem with the project
The code can’t prompt out, and all classes don’t jump with the method of Ctrl + click
There is an error as shown in the figure
Search found that, roughly because the project file is missing
Solution: find the. Project file in the root directory of the project, modify it, and add JDT support. My project is modified as shown below
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
<name>V4</name>
<comment></comment>
<projects>
</projects>
<buildSpec>
<buildCommand>
<name>org.eclipse.jdt.core.javabuilder</name>
<arguments>
</arguments>
</buildCommand>
</buildSpec>
<natures>
<nature>org.eclipse.jdt.core.javanature</nature>
<nature>org.apache.ivyde.eclipse.ivynature</nature>
</natures>
</projectDescription>
Similar Posts:
- After modifying Tomcat’s server.xml, the Tomcat deployment project reported an error: removing observe files from server… Could not clean server
- Invalid project name: Project “XXX” already exists
- Solve the initialization Java tooling exception information when eclipse starts
- When using eclipse to compile projects with JNI, make: * no rule to make target ` all ‘. Stop. Solution appears
- Some projects cannot be imported because they already exist in the workspace
- [Solved] Eclipse Start Error: an error has occurred see the log file
- The solution of “unsupported major. Minor version 52” in Java project compilation
- Eclipse Off-line Install activiti Plug-in error: “An error occurred while collecting items to be installed session conte…
- [Solved] Failed to read artifact descriptor for org.apache.
- android library projects cannot be launched