jamesnetherton opened a new pull request, #9105: URL: https://github.com/apache/camel-quarkus/pull/9105
Fixes #9104 `quarkus.camel.native.reflection.serialization-enabled` changes from `boolean` to `Optional<Boolean>`: - **unset** (the new default) — classes are registered for serialization only if an extension on the classpath requires it. This is the existing behaviour. - **`true`** — the base set is always registered. Unchanged. - **`false`** — nothing is registered, even when extensions require it, and the build logs a warning. Applications that set the option to `true`, or never set it, are unaffected. Only an explicit `false` changes meaning. `CamelSerializationBuildItem` now carries additional class names, so extensions can route all of their serialization registrations through it rather than producing `ReflectiveClassBuildItem.serializationClass(..)` directly, making the option a single point of control. `ManagementProcessor` is moved over accordingly, with no change to what it registers. `SqlProcessor` drops a `LinkedHashMap` registration that is already part of the base set. Documentation is updated to match, including a 3.40.0 migration guide entry, and the `extensions/sql` note that incorrectly told users they must enable serialization themselves. Verified with native builds of `integration-tests/management` in both states: with the veto applied the warning is logged and the build succeeds, and with the option unset `ManagementIT` passes. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
