You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2022/06/27 07:50:03 UTC
[GitHub] [camel-quarkus] apupier opened a new issue, #3876: Add camel-debug automatically in quarkus:dev mode
apupier opened a new issue, #3876:
URL: https://github.com/apache/camel-quarkus/issues/3876
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
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] apupier commented on issue #3876: Add camel-debug automatically in quarkus:dev mode
Posted by "apupier (via GitHub)" <gi...@apache.org>.
apupier commented on issue #3876:
URL: https://github.com/apache/camel-quarkus/issues/3876#issuecomment-1591253083
triggered discussion on Quarkus Zulip: https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/Adding.20a.20specific.20dependency.20only.20in.20dev.20mode
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] jamesnetherton commented on issue #3876: Add camel-debug automatically in quarkus:dev mode
Posted by GitBox <gi...@apache.org>.
jamesnetherton commented on issue #3876:
URL: https://github.com/apache/camel-quarkus/issues/3876#issuecomment-1167361627
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.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [camel-quarkus] essobedo commented on issue #3876: Add camel-debug automatically in quarkus:dev mode
Posted by GitBox <gi...@apache.org>.
essobedo commented on issue #3876:
URL: https://github.com/apache/camel-quarkus/issues/3876#issuecomment-1176431125
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` are also needed to be able to call `dumpModelAsXml` which means that one them should also be moved into the core and I guess that it is not wanted.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org