redhat-developer / redhat-developer/vscode-java

A single file ever opened with compilation error will influence the workspace

Open
#656 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Cannot get rid of a single file ever opened

steps to repro:

  1. Open 1.helloworld project in vscode at https://github.com/vscjavaci/java-debug-ci/tree/master/testcase/1.helloworld
  2. Create a Single.java outside the 1.helloworld folder
public class Single {
    public static void main(String[] args) throws IOException  {
 
        System.out.println("Program Arguments:");
        for (String arg : args) {
            System.out.println("\t" + arg);
        }            
        String foo = (String) System.getProperties().get("foo");
        System.out.println("\tValue:" + foo); 
    }
}
  1. Open the Single.java and F5 and then CLOSE the Single.java
  2. Trigger the force java compilation and choose "full"

expected: you will pass the compilation
actual: you will receive the build error notificaiton

image

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

Reproduce the issue using the 1.helloworld project linked in the report: create and open Single.java, run it with F5, close it, then trigger force java compilation with “full”. Trace how the closed file remains in the workspace compilation state; done means the full compilation passes without the closed file’s error.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript, vscode
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.