redhat-developer / redhat-developer/vscode-java
Absolutely no imports resolving on working maven project
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
This issue began on its own.
With no setting changes or recent updates to vscode or the red hat extension
- Operating System: mac OS 12.3.1
- JDK version: 1.8.0_333
- Visual Studio Code version: 1.78.2
- Java extension version: most recent 2 versions, as well as pre release
I cannot provide steps to reproduce. Every project is behaving strangely, including generating a bin folder (unless autobuild is disabled). Projects still appear under maven projects, and succeed when lifecycle phases are run. No imports, including those within the java package (such as String) are resolving.
logs.txt
I have tried:
Disabling all extensions except Java extension pack
Cleaning workspace
Manually Cleaning workspace
Reinstalling vscode entirely
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 reviewing the attached logs.txt and the reported Maven project behavior in the VS Code Java extension. Reproduce the failure with the stated macOS, JDK, VS Code, and extension versions, then verify that standard Java imports resolve while Maven lifecycle phases continue to succeed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100