jerboaa commented on issue #8061:
URL: https://github.com/apache/camel-quarkus/issues/8061#issuecomment-3718243140

   @ppalaga The intention of https://github.com/quarkusio/quarkus/pull/51432 
was to support graal master native builds (pass native integration tests of 
quarkus with a graal master build from source build). Graal master turns on 
complete reflection types by default. Can be "simulated" with a Mandrel 25 
release and adding 
`-Dquarkus.native.additional-build-args-append="--future-defaults=all`. It's 
intention is not to support the new metadata format.
   
   Note that https://github.com/quarkusio/quarkus/pull/51432 caused an issue in 
kotlin as well. See https://github.com/quarkusio/quarkus/issues/51503 and it 
appears it causes more issues in camel. The fix for 
https://github.com/quarkusio/quarkus/issues/51503 is 
https://github.com/quarkusio/quarkus/pull/51538 and it looks like a similar 
type filter would be needed for camel to put an upper bound of the 
implementations of interfaces being pulled in when a native image is being 
generated. E.g. you could filter interfaces in `org.springframework.core.io` 
for reflective access. Have you tried that?


-- 
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