davsclaus commented on PR #26709: URL: https://github.com/apache/camel/pull/26709#issuecomment-5767191747
Addressed the review in 3207ae6e726b: `defaultPostProcessors` is now an eager `final` field and the null-check branch in `postCompile` is gone. camel-groovy 108 tests green, full-reactor `mvn clean install -DskipTests` from the root green with no regen drift. PR body updated to drop the stale "depends on #26678" note. On the question about registry-vs-built-ins: keeping the registry as the single override point was deliberate. It mirrors what `RouteBuilderLoaderSupport` does for the Java DSL (registry processors only, camel-jbang supplies them), so both loaders behave the same and there is one rule to explain. Running the built-ins *in addition* to the registry would double-bind in camel-jbang, which registers the very same three classes plus the Spring/Quarkus ones, and filtering by class would make the rule harder to state. Anyone registering a custom `CompilePostProcessor` in a non-CLI runtime can bind the now-public camel-support processors alongside it, which is why the upgrade guide names them. Leaving as-is. _Claude Code on behalf of davsclaus_ -- 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]
