redhat-developer / redhat-developer/vscode-java
Sometimes several objects are shown in red after a small change, saying it can not find the type
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
[provide a description of the issue]
Environment
- Operating System: Fedora 33
- JDK version: 11.0.2
- Visual Studio Code version: 1.52.1
- Java extension version:
Steps To Reproduce
- [step 1]
It doesn't happen always, but happens often. To change one type somewhere and that triggers something and shows lots of classes as not found.
https://user-images.githubusercontent.com/1836434/104616247-59fa8d00-568a-11eb-8a29-31159179c0d4.mp4
- [step 2]
[Please attach a sample project reproducing the error]
https://github.com/jonathanvila/windup-operator
Please attach logs
languag-server.log
Basically this is the error inside :
org.osgi.framework.BundleException: Exception in org.eclipse.lsp4mp.jdt.core.MicroProfileCorePlugin.stop() of bundle org.eclipse.lsp4mp.jdt.core.
at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:891)
at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:1025)
at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:370)
at org.eclipse.osgi.container.Module.doStop(Module.java:660)
at org.eclipse.osgi.container.Module.stop(Module.java:521)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1886)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1761)
at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:275)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:202)
at org.eclipse.osgi.container.Module.doStop(Module.java:660)
at org.eclipse.osgi.container.Module.stop(Module.java:521)
at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:207)
at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:220)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.lang.IllegalStateException: Workspace is closed.
at org.eclipse.core.resources.ResourcesPlugin.getWorkspace(ResourcesPlugin.java:432)
at org.eclipse.lsp4mp.jdt.internal.core.MicroProfilePropertiesListenerManager.destroy(MicroProfilePropertiesListenerManager.java:245)
at org.eclipse.lsp4mp.jdt.core.MicroProfileCorePlugin.stop(MicroProfileCorePlugin.java:39)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:871)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:863)
... 13 more
Root exception:
java.lang.IllegalStateException: Workspace is closed.
Current Result
Expected Result
Additional Informations
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 windup-operator sample project and reproduce the issue by changing a type, then inspect language-server.log alongside the provided video. Trace the Workspace is closed exception and verify that classes no longer appear as missing after a small change, with the reported environment documented for comparison.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100