redhat-developer / redhat-developer/vscode-java
Unresolved Imports in VSCode, Maven itself works fine
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Environment
- Operating System: Windows Server 2012 (Remote SSH to SLES15)
- JDK version: openjdk version "11.0.3" 2019-04-16
- Visual Studio Code version: 1.58.2 user setup
- Java extension version: 0.80
Does the extension not use https://github.com/microsoft/vscode-maven to build a Maven project?
When using the Maven GUI option (basically mvn validate -f "...") everything works fine, but vscode-java reports unresolved types/imports.
The project uses Maven plugin Tycho which manages all dependencies and is automatically invoked by maven.
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 reproducing the project import in VSCode and compare it with the Maven GUI command mvn validate -f "..." described in the issue. Focus on how the Tycho-managed dependencies are resolved and whether that explains the unresolved imports; done means the project reports no false unresolved types or imports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100