Croway opened a new pull request, #30271:
URL: https://github.com/apache/camel/pull/30271

   Backport of #30236 to camel-4.22.x.
   
   Cherry-pick (`git cherry-pick -x`) of 2c2d09516feb (CAMEL-27077: 
camel-quartz - a scheduler from the registry gets the CamelContext when the 
component starts). With a Quartz `Scheduler` set on the quartz component or 
autowired from the registry, such as the scheduler of 
spring-boot-starter-quartz that Spring starts before Camel, the component now 
stores the CamelContext in that scheduler when it starts, so a trigger that 
fires before the CamelContext is fully started no longer fails with "No 
CamelContext could be found"; it logs a WARN when that scheduler is already 
running, and when `properties`, `propertiesRef` or `propertiesFile` are set, as 
they are not used then.
   
   Adjustments:
   - The hunk of `camel-4x-upgrade-guide-4_24.adoc` is left out: the file does 
not exist on this branch, and the upgrade guides are published from main, where 
the 4.22.3 note is added separately.
   - The commit message is the one of the main commit plus the cherry-pick 
line: the main commit has no `Co-authored-by` trailer to drop.
   - `QuartzComponent`, `QuartzInjectedSchedulerTest`, `quartz-component.adoc` 
and its catalog copy apply unchanged. The diff is the same as the one of the 
main commit, without the upgrade-guide hunk.
   
   Tests, on camel-4.22.x with JDK 25 (`mvnd test -pl components/camel-quartz 
-am 
-Dtest='org/apache/camel/component/quartz/**/*Test*,org/apache/camel/pollconsumer/quartz/**/*Test*,org/apache/camel/routepolicy/quartz/**/*Test*'`):
 all 71 test classes of camel-quartz, 108 tests, 0 failures, 0 skipped. 
`QuartzInjectedSchedulerTest`: 5 tests pass. The build leaves no uncommitted 
change (formatter, impsort).
   
   _Claude Code on behalf of Federico Mariani_
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to