redhat-developer / redhat-developer/vscode-java

Stuck at "Building: 0% [0/1000]" in "Task - Java Build Status"

Open
#1,739 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

ls-error/crash
Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

I wrote a Maven plugin to generate .class files and a .jar from OpenOffice .idl files.
When i open the workspace which uses said plugin the project compiles fine and auto completion works. But when i edit one of these .idl files autocompletion stops working and i'm getting stuck at "Building: 0% [0/1000]" in "Task - Java Build Status". The goal of my Maven plugin will still finish tho, so the issue seems to occur after my plugin finishes execution.
My Maven plugin uses the "META-INF/m2e/lifecycle-mapping-metadata.xml" file to make the plugin compatible with eclipse.
I also made sure that there's no compilation if nothing actually changed. I can run mvn install as often as i want and it won't change the modification dates of any of my generated files.

It would be nice if someone could show me how to debug the task "Java Build Status" so i can figure out what's wrong.

I'll try to somehow create 2 sample projects to reproduce if there is no way to debug it myself.

Environment
  • Operating System: openSUSE Leap 42.2
  • JDK version: 11.0.8, 2020-07-14
  • Visual Studio Code version: 1.50.0, 2020-10-07
  • Java extension version: 0.72.0, [2020-12-02]

Screenshot_20201211_110403

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 reproducing the stalled “Java Build Status” with a workspace using the reported Maven plugin and its META-INF/m2e/lifecycle-mapping-metadata.xml file. Compare behavior before and after editing an OpenOffice .idl file, and use the requested debugging path to identify why autocomplete stops; done means the build status completes and autocomplete remains available after the plugin runs.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, vscode
Domain
build-system, developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.