You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2023/10/23 13:24:00 UTC
[jira] [Assigned] (CAMEL-19437) Provide a profile to activate Camel Route debugger when generating Camel Quarkus project with Camel JBang export
[ https://issues.apache.org/jira/browse/CAMEL-19437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen reassigned CAMEL-19437:
-----------------------------------
Assignee: Claus Ibsen
> Provide a profile to activate Camel Route debugger when generating Camel Quarkus project with Camel JBang export
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-19437
> URL: https://issues.apache.org/jira/browse/CAMEL-19437
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Affects Versions: 3.20.5
> Reporter: Aurélien Pupier
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.2.0
>
>
> Currently the `camel-quarkus-debug` dependency must be added to the classpath to activate Camel Route Debugging for Camel Quarkus.
> it would be nice that the Camel JBang export command is providing a profile named `camel.debug` containing this dependency.
> It will improve User Experience in VS Code using VS Code Language Support for Apache Camel and VS Code Debug Adapter for Apache Camel extensions.
> Note:
> * camel-quarkus-debug is available since Camel Quarkus 2.10.0 https://github.com/apache/camel-quarkus/issues/3775
> * activating it automatically in debug mode seems not possible [https://github.com/apache/camel-quarkus/issues/3876]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)