quarkus-camel - Use MainSupport as base for running Camel about camel-quarkus HOT 3 CLOSED

As today core is responsible to act like a main but for better flexibility (i.e. for other to build on top of core) I think we need to split responsibilities like:

1. core to set-up low level things such as:
   • camel context
   • registry
   • integration with quarkus event loop #131
2. main to set up application related things, like:
   • initialize, start/stop the camel context created by core
   • discover routes
   • discover and register life-cycle interceptors (to allow i.e. camel-k to hook into the static init build processors)
   • integration with quarkus health checks #141
   • integration with quarkus metrics #128
   • fire CDI events

/cc @gnodet @davsclaus

from camel-quarkus.

This should be easier to do now that we are on Camel 3.0.0.M4. Any hints or examples @davsclaus how to do that?

from camel-quarkus.

Fixed by #226

from camel-quarkus.