A new release of VS Code Language Support for Apache Camel 0.1.0 is available. It includes upgrade of Camel catalogs, removal of Java 8 as runtime for embedded Language Server, connected mode completion for Kubernetes and Knative and folding of choice in Java.

Removal of Java 8 as runtime for embedded Language Server

The removal of Java 8 as runtime for embedded Language Server allowed the upgrade of Camel Quarkus Catalog and some test dependencies. Java 8 is planned to be dropped in several of current dependencies, including Camel. It is time to move forward.

Java 8 is still usable for the Camel projects themselves that support it. It will impact only the tooling provided through the Camel Language Server.

Connected-mode for completion of Knative and Kubernetes components

When a kubernetes connection is configured, either via command-line interface or by VS Code Kubernetes extension, the completion is looking up in the Kubernetes instance for the following cases: * namespace attribute value on kubernetes-* components completion for namespace attribute * endpoint, channel and event component path values on knative component completion for channel value

Camel catalogs version upgrades

The default Camel catalog has been upgraded from 3.11.1 to 3.12.0.

The Kamelet catalog has been upgraded from 0.3.0 to 0.4.0.

The Camel Quarkus catalog has been upgraded from 2.0.0 to 2.3.0.

The Camel kafka connector catalog has been upgraded from 0.10.1 to 0.11.0.

Folding of Camel routes in Java editor

In previous release, it was possible to fold a Camel route. It is now possible to fold each choice of Camel routes in the java editor.

Example to fold choice Camel route in Java Editor of VS Code

What’s next?

Provide your feedback and ideas! You can start discussions on Zulip camel-tooling channel. You can create and vote for issues on github Camel Language Server, VS Code Language support for Apache Camel. You can create and vote for issues on the jira used by the Red Hat Integration tooling team.