Simplify vscode-java-test installation instructions in README

[gbroques]

Problem Statement

I recently setup this plugin for debugging JUnit tests with vscode-java-test, and ran into an issue following the instructions in the README. Particularly with the npm run build-plugin step since vscode-java-test depends on a SNAPSHOT version of JDTLS.

See microsoft/vscode-java-test#1580 and microsoft/vscode-java-test#1581 for details.

I noticed looking at @mfussenegger's configuration, linked to from the Wiki, that they also had trouble with this step:
https://github.com/mfussenegger/dotfiles/blob/833d634251ebf3bf7e9899ed06ac710735d392da/vim/.config/nvim/ftplugin/java.lua#L109-L110

-- npm install broke for me: npm/cli#2508
-- So gather the required jars manually; this is based on the gulpfile.js in the vscode-java-test repo

See discussion #329 for other problems with vscode-java-test bundles.

Building the bundles for vscode-java-test may require a certain version of Java, npm / Node.js, and fail for an unknown reason.

Ideas or possible solutions

A better way could be to download the pre-built bundles from the latest release.

For example, we can download the vscjava.vscode-java-test-0.39.0.vsix file, extract it, and specify the path to /extension/server/.

---

SEE ALSO: Discussion #521

[gbroques]

Unfortunately, the vscode-java-test team stopped providing prebuilt assets for their GitHub releases starting with 0.39.1.

See:
microsoft/vscode-java-test#1594 (comment)

[gbroques]

The Mason registry also depends on this vsix asset, and @williamboman had the following to say:

I've been meaning to host built assets for these projects...

See mason-org/mason-registry#3083 (comment).

From that same pull-request thread, someone created a project to build and host vscode-java-test artifacts:
https://github.com/nvim-java/vscode-java-test-releases

See mason-org/mason-registry#3083 (comment).

I'll wait on this issue, and update the README.md based on wherever the Mason registry chooses to download a prebuilt vscode-java-test artifact from.

[gbroques]

A quick update on this.

The Mason registry is sourcing these pre-built artifacts from the Open VSX registry:

• bump up java-test to 0.40.1 mason-org/mason-registry#3348 (comment)
• mason-org/mason-registry@310c621

I can work on a PR for this issue when I find time.

[IlyasYOY]

I found an interesting case.

I have a test like:

package com.example.demo;

import org.junit.jupiter.api.Test;
import org.springframework.boot.test.context.SpringBootTest;

@SpringBootTest
class DemoApplicationTests {

    @Test
    void contextLoads() {
        System.out.println("lol");
    }

}

Test above is not working when I run it with test_nearest_*.

But if I change name of the file to be the same as the test class — everything works like a charm.