Open apupier opened 2 years ago
Maybe I took the wrong approach in creating a dedicated extension for camel-debug
.
Perhaps it would be better if we add camel-debug
as a direct dependency to camel-quarkus-core-deployment
. Then moved the BuildStep
s that are in camel-quarkus-debug
into the core. I think that would allow users to not have to explicitly add the debug dependency and also prevent the debug bits leaking outside of dev mode.
Even if, we could move camel-debug
and camel-management
into core, it would not be enough to make the Camel Debugger works properly as camel-quarkus-xml-jaxb
or camel-quarkus-xml-io-dsl
is also needed to be able to call dumpModelAsXml
which means that one them should also be moved into the core and I guess that is something that we don't want.
triggered discussion on Quarkus Zulip: https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/Adding.20a.20specific.20dependency.20only.20in.20dev.20mode
Would the approach used here to add the camel-debug on classpath automatically https://github.com/apache/camel/pull/7877/files#diff-893d81229b9e254f8dfe5b3b291d713387666add70d56cf8584b95d7a1a6f8d8R114 be possible in Camel Quarkus too?
Or maybe we would need a specific Mojo binding which is wrapping the quarkus:dev?
follow-up on https://github.com/apache/camel-quarkus/issues/3775