1.7.0 not working for me anymore

[Qichar]

Hello,

I recently brought down both the client and server repos so that I could build java-1.7.0.vsix
(following your contributing instructions:
https://github.com/redhat-developer/vscode-java/blob/master/CONTRIBUTING.md)

You may ask, why not the latest? For various reasons I cannot not use Java 17, the latest version I can use is 11. So I can't use versions of vscode-java after 1.7.0.

I pulled the code from this git repo and I was able to perform a successful npm install. I believe I can build the client side part of the extension just fine. However, for several reasons I cannot use the server side code that matches 1.7.0 client. The server version that I think matches is 1.12.0, because it was released within a day of the client and the CHANGELOG.md notes are identical. But could not build the server version 1.12.0 due to this issue:
eclipse-jdtls/eclipse.jdt.ls#2128

Even after changing inside of org.eclipse.jdt.ls.target/org.eclipse.jdt.ls.tp.target

to:

I got errors when attempting to npm run build-server. I was only able to build the latest (master) of the https://github.com/eclipse/eclipse.jdt.ls repo.

Therefore, I tried to combine version 1.7.0 of the client with the latest version of the server (at that time, master), I got an error.

When I deployed this extension along with Theia, I got the following error:

Promise rejection not handled in one second: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed , reason: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
With stack trace: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
at doWrite (_stream_writable.js:399:19)
at writeOrBuffer (_stream_writable.js:387:5)
at Socket.Writable.write (_stream_writable.js:318:11)
at /private/var/folders/yg/kw840kb525v7syr8w3dfq37m0000gn/T/vscode-unpacked/java-1.7.0.vsix/extension/dist/extension.js:2:1054691
at new Promise ()
at c.write (/private/var/folders/yg/kw840kb525v7syr8w3dfq37m0000gn/T/vscode-unpacked/java-1.7.0.vsix/extension/dist/extension.js:2:1054609)
at _.doWrite (/private/var/folders/yg/kw840kb525v7syr8w3dfq37m0000gn/T/vscode-unpacked/java-1.7.0.vsix/extension/dist/extension.js:2:1044160)
at /private/var/folders/yg/kw840kb525v7syr8w3dfq37m0000gn/T/vscode-unpacked/java-1.7.0.vsix/extension/dist/extension.js:2:1044055

Some background: Before attempting to build the java-1.7.0.vsix myself, I had tested the one I downloaded from the releases section of this repo:
https://github.com/redhat-developer/vscode-java/releases/download/v1.7.0/java-1.7.0.vsix

This worked fine in Theia. I could see the syntax errors, and they would also appear listed under the Problems tab.

However, when I tried to use my own built version of java-1.7.0.vsix, I noticed that it would tell me at the bottom of Theia:
"Activating Language Support for Java (TM) by Red Hat". At the bottom right, next to the word "java", there is a little spinny and it spins forever. The vscode-java extension I built never loads. This was after I opened a small .java file. If I start Theia without having such a file open, it does not yet attempt to load the extension. Attempting to load the extension is apparently triggered by opening a .java file. Along with the symptoms seen in the UI, I got the error I pasted above in my Theia console output. (I was running Theia locally from my IDE).

OK, so I thought I simply built the .vsix incorrectly. However, now, even using the "official release" java-1.7.0.vsix from your repo I get the same problem. I get that message and the spinny in the bottom right spins forever. It looks EXACTLY like the symptoms described in this issue:
#2405

I read through that discussion, but I am running Theia, not Visual Studio Code, and I don't have a workspace per se. I am only opening a single .java file. It's almost as if I corrupted my machine / dev environment somehow and I can't go back to a clean slate.

Other notes:

• going back to version 1.6.0 of the extension works just fine.
• no matter what I do (including completely getting rid of my Theia repo and building it from scratch (download all plugins including the java-1.7.0.vsix anew), I can't get the official release (downloaded) version of java-1.7.0.vsix to work anymore.
• I gave the official release version of java-1.7.0.vsix to a co-worker, and he is able to get it running inside of Theia without problems, just like I used to be able to do.

It seems my machine has entered some kind of "bad state". My question is, how do I get it working again? I cannot use a different version, it must be java-1.7.0.vsix. Is there some browser cache, or something else I can get rid of to start over from scratch? Something is remembering me, and I have no idea what it is.

On a side note, I would love to know how the server-client interaction between the two pieces of this java language extension works. when I run this extension in Theia, is it going to some language server out on the internet? I did not do anything to set up my own language server, I only dropped the extension into my Theia git repository and built Theia, downloaded the plugins, and ran it in a browser on my local machine.

I'm so sorry this is so long! I thought by providing lots of details it would be easier to debug this issue. Thank you for your patience, and I hope to hear from you soon!