Java language support not working in Apache Camel K worskpace

[Katka92]

Describe the bug

The Java language support is not working in default Apache Camel K workspace. Functions like Ctrl + click to e.g. open a class or go to the definition does not work, error highlighting does not work.

Che version

• latest 7.9.0
• other: 7.8.0

Steps to reproduce

1. Go to Workspace -> Add Workspace
2. Choose Apache Camel K workspace
3. Create and run the workspace with default settings
4. Open any Java file (e.g. polyglot -> JavaRoute.java)
5. Try Ctrl + click on info on line 23 - nothing happens
6. Insert new line 24, type error - no error highlighting

Expected behavior

Error highlighting and code navigation should work.

Runtime

• other: Che version 7.9.0 on openshift, https://che.prod-preview.openshift.io with version 7.8.0

Screenshots

Installation method

• chectl for 7.9.0

Environment

• Cloud
  • Amazon for Che with 7.9.0 version
• other: for che.prod-preview.openshift.io

[tolusha]

I believe these kind of issues must contain workspace logs.
Currently it is easy to get them using checlt workspace:logs -w <id> -n <namespace> command.

[Katka92]

@tolusha So this is the output of the command you've sent.

events.txt
verifier.log
che-machine-exec2jx.log
mysql.log
theia-idepvi.log
vscode-javae9k.log

[tolusha]

Probably Java ls in't initialized.
Could you refresh the tab to check if it helps?

[Katka92]

I tried to reopen file and nothing changed, but after the refresh, I saw this pop-up.

[l0rd]

It looks like the Camel K plugin doesn't work with the version of Kube you are running on. @Katka92 what's exactly the OpenShift version? cc @apupier @bfitzpat

[apupier]

In the Camel K Dev file, Java language support is not provided https://github.com/eclipse/che-devfile-registry/blob/master/devfiles/apache-camel-k/devfile.yaml . We will surely need to play with memory to fit in the 3G memory limits of che.openshift.io as the Kubernetes side is already taking 1G

The Java language support is really limited currently in the absolute. Even if the Java language support is activated, as it is a standalone file you will have only syntax validation. VS Code Java 0.55+ is required to have proper Java support which is a version not yet available in Che.
see #15560 (comment)

What Camel K is providing is Camel URI completion in Camel K Standalone files.

For the kubectl error, seems effectively that the kubectl version is not compatible with the Kubernetes/OpenShift version you are trying to connect to.
The kubectl version is coming from Kubernetes sidecar https://github.com/che-dockerfiles/che-sidecar-kubernetes-tooling/blob/1.0.4/Dockerfile#L13

[apupier]

created for including Java in Camel K stack #16018

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[apupier]

/remove-lifecycle stale

[ericwill]

Is this one still relevant @apupier? Or can we close it and use #16018

[apupier]

ok to use #16018