jamesnetherton opened a new issue, #8061: URL: https://github.com/apache/camel-quarkus/issues/8061
Relates to a recent change in Quarkus (I think): https://github.com/quarkusio/quarkus/pull/51432/files#diff-dd653239270235387ddd13cef504ec87293843568fb75b1949308124ae77553f I think having `quarkus-jaxb` on the classpath is potentially an issue in some cases. It seems to widen the closure of classes that the native compiler discovers. For example in the `netty-http` integration tests we have `quarkus-jaxb` on the classpath to test the Camel REST DSL with XML payloads. When compiling the native application there a now various errors relating to Netty SSL classes. It's a similar case for `cxf-soap` tests. There are errors relating to BouncyCastle and Spring. There was an issue with `hashicorp-vault`, but I was able to remove JAXB and fix the issues in #8056. What worries me, is how do we know our extensions will successfully compile in native mode if `quarkus-jaxb` is on the classpath? We only have it in our tests where required. There's nothing to stop users adding it manually in their apps. I have attached the CI logs for the failing tests: [native-group1.txt](https://github.com/user-attachments/files/24084516/native-group1.txt) [native-group5.txt](https://github.com/user-attachments/files/24084517/native-group5.txt) -- 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]
