lburgazzoli commented on issue #1128:
URL: https://github.com/apache/camel-quarkus/issues/1128#issuecomment-626512952
I'm workign on a big refactor :)
This is an automated message from the Apache Git Service.
To respond to
lburgazzoli commented on issue #1128:
URL: https://github.com/apache/camel-quarkus/issues/1128#issuecomment-624482779
Additional note, there is an
[issue](https://issues.apache.org/jira/browse/CAMEL-14600) about move component
auto configuration as part of standard component life-cycle
lburgazzoli commented on issue #1128:
URL: https://github.com/apache/camel-quarkus/issues/1128#issuecomment-624100328
@ppalaga are the info here good enough to start working on the
implementation ?
This is an automated
lburgazzoli commented on issue #1128:
URL: https://github.com/apache/camel-quarkus/issues/1128#issuecomment-621931531
> 1. According to your proposal, our non-core extensions will depend on
`camel-quarkus-core` (rather than `camel-quarkus-main`), right?
correct
> 2. Our
lburgazzoli commented on issue #1128:
URL: https://github.com/apache/camel-quarkus/issues/1128#issuecomment-620408825
yeah, something like that but we need to think a little about it
This is an automated message from the
lburgazzoli commented on issue #1128:
URL: https://github.com/apache/camel-quarkus/issues/1128#issuecomment-619710128
> > provide a default "bootstrap item" that start the camel context
>
> So this is the same as the CamelMain.start() currently ?
Except it does not use
lburgazzoli commented on issue #1128:
URL: https://github.com/apache/camel-quarkus/issues/1128#issuecomment-618407713
@ppalaga updated the issue
This is an automated message from the Apache Git Service.
To respond to the
lburgazzoli commented on issue #1128:
URL: https://github.com/apache/camel-quarkus/issues/1128#issuecomment-618288229
I think you get this wrong as my proposal is to revisit the boostrap in
general so if you don't have main as extension, then camel will still start the
camel context and
