Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Major
Fix Version/s: 2.4.0.GA
Affects Version/s: 2.4.0.GA
Component/s: plugins: registries, factories, git
Labels:
None

Blocked:
False
Ready:
False
Release Note Text:
Undefined
Steps to Reproduce:
Hide

Just open the SpringBoot / Thorntail workspace, click on any java files, you will be notified that LS can't be activated.

But you can avoid this by adding the following config to devifile.yaml:

id: redhat/java8/latest
    type: chePlugin
    env:
      - name: JAVA_HOME
        value: /usr/lib/jvm/java-1.8.0-openj9
Show
Just open the SpringBoot / Thorntail workspace, click on any java files, you will be notified that LS can't be activated. But you can avoid this by adding the following config to devifile.yaml: id: redhat/java8/latest type: chePlugin env: - name: JAVA_HOME value: /usr/lib/jvm/java-1.8.0-openj9
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

After deploying the crw2.4 on OCP, And make sure the devfiles.yaml(in devfile registry) and meta.yaml(in plugin registry) is pointing to the updated image which is
quay.io/crw/plugin-java8-openj9-rhel8@sha256:14f2774e92b70d85280e506f81e2ea9a89c26490fd53a4421df8a694bd944d2d

It seems the image it is pulling in maven and vscode-javav8t container is still the outdated one.

And the LS can't be activated because the java-home is not pointing to the
/usr/lib/jvm/java-1.8.0-openj9