redhat-developer / redhat-developer/vscode-java
"Incomplete classpath" in ant project
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
First time user of VS Code, and it's been some time since I last worked with Java, so apologies for any gaps in my knowledge. I have a project where a colleague set up an ant build file and I'm trying to build it in VS Code. I'm getting the infamous "Classpath is incomplete" warning as described here: https://github.com/redhat-developer/vscode-java/wiki/%22Classpath-is-incomplete%22-warning.
The question is about how to resolve this, i.e. to complete the classpath, while still having this be an ant-built project as my colleague intends. The last paragraph of the wiki article says "You need to open a folder containing a pom.xml, build.gradle or at least default eclipse setting files, so that a complete classpath and project hierarchy can be set." I assume that if I put the correct "default eclipse setting files" in my project folder I can make the error go away -- is that right? If so, what should be in those default eclipse setting files? Could you edit the Wiki page to give guidance or at least a link to somewhere explaining what to do next?
Environment
- Operating System: Windows 10
- JDK version: 1.8.0_221
- Visual Studio Code version: 1.37.1
- Java extension version: Java Extension Pack 0.7.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked “Classpath is incomplete” wiki article and the question’s Ant-project context. Update the wiki guidance to explain what an Ant project needs for a complete classpath, including whether default Eclipse setting files are sufficient and what they should contain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100