vscode-java-pack | VS Code extensions for Java developers

A similar question was asked for Eclipse: Add Java Docs in Eclipse working on OpenJDK

I found /usr/lib/jvm/java-11-openjdk-amd64/lib/src.zip on my system.

Building and runing a source file works. Documentation is shown for dependencies loaded via Maven. The documentation for the Java standard library is missing.

Examples:

hovering over

Visual Studio Code doesn't resolve dependencies declared in my build.gradle.kts file in this test project. Can you help me see what I'm doing wrong?

I'm using the newest VScode (downloaded 1.52.1 yesterday), and I've started from a clean install by deleting %APPDATA%\Code and %USERPROFILE%\.vscode before starting VScode.

When opening up my Java file and installing various suggested extensions (see below), I end up seeing The import org.keycloak cannot be resolved:

which is true for any dependencies from build.gradle.kts. Notice how java.util.List is fine.

gradle builds the project fine, even from within VScode:

Also, "Java Projects" shows "Referenced Libraries" as empty:

I suspect that an empty "Referenced Libraries" is related to not resolving org.keycloak above.

The exact same project is fine when opened in Intellij.

I've used this test project, and after installing various suggested extensions, I ended up with this list from code --list-extensions:

I have been assigned to a project that builds some Eclipse plugins. There is a root pom.xml, and maven builds it successfully. But when I load it into VSCode, with the Java Pack (vscjava.vscode-java-pack) loaded, and load the Java projects, many files produce errors like

I am using a VSCode devcontainer to write a Java application. I put it down for about a month, came back to work on it and now I'm getting some unfamiliar errors.

Here I'll provide my relevant configuration files for my devcontainer environment.

My Dockerfile is as below:

I'm using VSCode Devcontainers to develop a micro-services application and I've been using a Java Devcontainer without issues. But, given the micro-service nature of the project, there are other containers I need to execute (for instance, a postgres db). This is the only container I use to develop, where I install Java-specific extensions, intellisense working, etc. I do NOT have this on my local machine nor do I want to have. Only when coding on the container.

Now, I did some research to shift the use of Devcontainers to docker-compose and start not only the Java devcontainer but also the database. Everything seems to run fine. However, the dev container will alway exit with code 137 and I can't figure out why.

The structure of the code is as follows:

I am new to spring-boot and decided to try out vscode as my editor via this setup tutorial from Microsoft.

I was able to get the basic application to run but I now have the following error. If I ignore the error, it still runs - but there is no actual problem that I can see since this is the boilerplate code from the tutorial.

Is this just a vscode thing? I had trouble using the built-in boot initializer extension vs the spring initializer website as well.

I haven't done code in a while and used to use eclipse, but wanted to try vscode. If vscode is known to be a buggy or problematic I'll go back to eclipse. Is there some additional setup for vscode and spring-boot I need to do be doing?

Also, not sure if this is related - but the MS doc above said to have maven preinstalled, but then it looks like the Java Extension Pack is recommends installed its own version?

Screenshot: