This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel.git
commit 2061fb49fc45a25e503a3cb969790b53e991107e Author: Claus Ibsen <[email protected]> AuthorDate: Mon Oct 23 15:39:20 2023 +0200 CAMEL-19437: camel-jbang - Export should include maven profile to include camel-debug for remote debugging from IDE tools --- docs/user-manual/modules/ROOT/pages/camel-jbang.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc b/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc index 3b5f07b7595..3316f00ccb0 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc @@ -1887,6 +1887,9 @@ You can then use the Integrated Development Environment (IDE) of your choice. Fo A specific how-to is available for VS Code, see this https://youtu.be/owNhWxf42qk[video] or this /blog/2022/05/start-camel-quarkus-application-with-camel-textual-debug-in-vscode/[blogpost]. +TIP: When exporting to Maven projects, then you can use the maven profile `camel.debug` that will include the `camel-debug` JAR +to make it possible for Camel IDE tools to do Camel route debugging. + ==== Health Checks The status of health checks can be accessed via Camel JBang from the CLI as follows:
