[
https://issues.apache.org/jira/browse/CAMEL-19437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731746#comment-17731746
]
Aurélien Pupier commented on CAMEL-19437:
-----------------------------------------
Exporting with --dep=camel:debug is covering another use case as it is adding
the dependency to the project as a normal dependency, so it means it will be
added at runtime for production (which is something that shouldn't be used as
far I know).
The goal is to have the project pre-configured with a specific profile for
Camel debugging without impacting the runtime in production.
> 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
> Priority: Minor
>
> 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)
