Installing Java Test Runner Support for Java

Issue

There seems to be no support for running Tests in Java on Che 7.

Adding the Java Test Runner extension would be a good solution to this problem as it would add support for both class level and function level tests.

Steps tried

• Tried installing the plugin by copying the Code Quick Open from here as suggested over here
  • The installation failed as the extension was dependent on redhat’s language support.
• Tried installing the plugin by publishing it as mentioned over here by publishing it.
  • The publishing instructions were not very clear. On stumbling about, found this page about customising the registries
• Tried editing the plugin registry at runtime as mentioned here.
  • The commands did not mention changing the namespace.
  • kubectl exec $\{PLUGIN_REG_POD} -i -t -- /var/www/html/index_v2.sh v3 > /var/www/html/v3/plugins/index.json did not work. It kept confusing the files by trying to find the file on my local machine.

Help regarding any of the above solutions is much appreciated.

Here are the issues that are keeping this extension from working properly in Che: [x] Support VS Code Standard Icons in Contributions https://github.com/eclipse-theia/theia/issues/7634 [x] Support Command Type for StatusBarItem.command https://github.com/eclipse-theia/theia/issues/8241 [x] Cannot resolve /hostedPlugin/ Resources from Sidecar Containers #17517

[thisHermit]

As you have moved this to a P2 priority, would you mind if I take this up?

If yes, can you please suggest me the steps I should take?

[tsmaeder]

The problem loading the “pass”, “running”, etc. icons is that the front end is trying to load an icon with an URI like this: https://routeij17ga9z-che.apps-crc.testing/hostedPlugin/vscode-java-test/resources/media/dark/pass.svg. This kind of icon is resolved locally to the Theia back end process in https://github.com/eclipse-theia/theia/blob/dfcfccc1d4cfa86534419dd28dfe86faab2c494b/packages/plugin-ext/src/hosted/node/plugin-reader.ts#L51. However, the icon would have to be read from the container running the plugin and there are no provisions for forwarding the request to the container.