redhat-developer / redhat-developer/vscode-java

"Starting java language server" processing stops before 100% on workspaces with a non-existing project directory (causing "Classpath is incomplete")

Open
#1,303 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

classpath
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

The following workspace opens ok and "starting java language server" process finishes at 100%

{
	"folders": [
        {
            "path":"simple-project1"
        },
        {
            "path":"other-existing-dir"
        }
    ]
}

However the one below one stops at 30% because the first project path in the workspace does not exist. This causes also the following error when clicking on the code of Main.java: "Classpath is incomplete: Only syntax errors will be reported":

{
	"folders": [
        {
            "path":"non-existing-dir"
        },    
        {
            "path":"simple-project1"
        },
        {
            "path":"other-existing-dir"
        }
    ]
}
Environment
  • Operating System: Ubuntu 18.04.3 LTS
  • JDK version: 13
  • Visual Studio Code version: 1.42.1
  • Java extension version: 0.57.0 (got from changelog)
Steps To Reproduce
  • First open working-workspace.code-workspace and see the thumbs-up symbol on down-right side.
  • Then open problematic-workspace.code-workspace and see the thumbs-down symbol on down-right side.
Current Result
Expected Result
Additional Informations

code-missing-project-path-issue.tar.gz

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by extracting code-missing-project-path-issue.tar.gz and opening working-workspace.code-workspace and problematic-workspace.code-workspace in VS Code. Reproduce the language-server startup with the non-existing project path first, then compare progress and diagnostics with the working workspace. Done means startup reaches 100% and Main.java no longer reports an incomplete classpath.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.