There are new releases of 3 VS Code extensions:
- Language support for Apache Camel 0.9.0
- Debug Adapter for Apache Camel 0.8.0
- Tooling for Apache Camel K 0.0.34
Notable Camel related version upgrades:
- Update Kamelet Catalog from 3.20.4 to 3.21.0
- Update default Camel Catalog version from 3.20.5 to 3.21.0
- Update default Camel version used for Camel JBang from 3.20.5 to 3.21.0
- Update default Camel K runtime version from v1.11.0 to v1.12.1
Completion for Camel Quarkus debug profile in pom.xml
It helps to configure a Camel on Quarkus application to use the Camel Route Textual debugger.
For an example of the whole process to use the Camel debugger with a Camel on Quarkus project, see this video.
Commands to create Camel on Quarkus and SpringBoot project
Two commands have been created to create Camel projects:
Camel: Create a Camel Quarkus project
Camel: Create a Camel on SpringBoot project
This first iteration is coming with a minimal configuration. Only the GroupID, ArtifactID and version of the new project is asked to the end-user. In case, there are some Camel routes at the root of the workspace, they are copied at the correct place in the created project.
Quick menu action on editor title to Deploy Integration with Apache Camel K
Previously, it was possible to deploy an integration with Camel K using command palette, contextual menu from the Explorer or a codelens in textual editor. A quick action has been added to the editor. It is very convenient when the editor used is a graphical one.
Settings for specifying the Camel version to run integrations with Camel JBang CLI
Previously, it was reusing the version of Camel Jbang version, it is now possible to also provide the Camel version.
It is planned to publish videos leveraging the new features in a more global scenario. Stay tuned and follow Demo of Red Hat Integration and Apache Camel Tooling playlist.
Please provide feedback and ideas with your preferred channel: