JiriOndrusek commented on PR #4119: URL: https://github.com/apache/camel-quarkus/pull/4119#issuecomment-1256272233
> I think we should consider this a temporary fix. It forces the Quarkus quartz scheduler to always be autowired into the Camel component, which I don't think is what we want as the default if no `quarkus.quartz` properties were defined (I.e Camel should create the scheduler itself in that scenario). Hi @jamesnetherton I proposed to the quarkus an "enhancment" to not create Quartz scheduler in case tat there is no `quarkus.quartz.*` property (or @Scheduled), but it seems, that this approach is not possible (see https://github.com/quarkusio/quarkus/pull/28168) I'll try to find a solution which does not require above change in quarkus. -- 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-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
