redhat-developer / redhat-developer/vscode-java
Classpath Incomplete Warning with Eclipse-generated project
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
I have a lot of projects created through Eclipse that work fine. They have buildpaths and classpaths very similar to a project I'm working on currently. I created the project, made some classes, and then started implementing stuff in VSCode when the Classpath Incomplete warning popped up. The .classpath file is in the project folder, along with the .project file. I have the default src folder with a package within it that has all the source code. Everything was setup using Eclipse.
Environment
- Operating System: Win10.something
- JDK version: 1.8.0_144
- Visual Studio Code version: 1.22.1
- Java extension version: 0.22.0
Steps To Reproduce
- Create a lot of projects in Eclipse.
- Write all of the source in VSCode.
- Have one project created in Eclipse repeatedly throw Classpath Incomplete warning in VSCode.
Current Result
ClassPath Incomplete warning thrown
Expected Result
No warnings being thrown
Additional Informations
If the warnings could include a diagnostic in a future version, that may help a lot.
And sorry, I can't provide a video because I can't post my source online anywhere.
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 by comparing the Eclipse-generated .classpath and .project files with the default src folder and its package, using the reported Windows, JDK 1.8.0_144, VS Code 1.22.1, and Java extension 0.22.0 environment. Reproduce the Classpath Incomplete warning and determine what project state triggers it; done means the warning is resolved or includes a useful diagnostic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100