microsoft / microsoft/vscode-java-pack
Build Errors disappear after opening file
Open
Nobody has claimed this yet.
ai-triaged
bug
reliability
- Dominant language
- TypeScript
- Stars
- 352
- Forks
- 166
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 32
Description
example projects:
- https://github.com/apache/jmeter.git
- https://github.com/hibernate/hibernate-orm.git
- https://github.com/apereo/cas.git
Steps to reproduce:
- Open one of the example projects in VS Code
- you can see many errors after project importing
- click one of the errors to open the java source file, the errors in this file are gone
We can see the errors are in test files and they just reference types in another project, using the following schema:
dependencies {
testImplementation project(path: ":XXX:XXXX", configuration: "tests")
}
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the issue by importing the listed JMeter, Hibernate ORM, or Apereo CAS projects in VS Code, then inspect the diagnostics before and after opening a Java source file. Start with the Gradle testImplementation project dependency pattern shown in the report; done should mean the expected diagnostic behavior is consistent before and after opening files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100