JiriOndrusek opened a new issue, #4722: URL: https://github.com/apache/camel-quarkus/issues/4722
Related to the issues https://github.com/apache/camel-quarkus/issues/4710 and https://github.com/apache/camel-quarkus/issues/4043 `camel-quarkus-xslt` brings transitively `xalan`fails on `java.lang.ClassNotFoundException: org.apache.hc.client5.http.impl.auth.NTLMEngineImpl`. This class is registered on 3 places in camel-quarkus: 1. `httpclient` -> here the registration happens only in case that the class is on classpath (seems like a riight approach to me) 2. in `XslProcessor` - without a condition 3. in 'SaxonProcessor` - without a condition As stated in https://github.com/apache/camel-quarkus/issues/4710, this registration could be "triggered" without the class on the classpath, which causes failure. From my PoV: 1. There should be a test covering such use case (which causes failure with the current codebase) 2. Registration should be triggered only with a condition similarly as in `httpclient` module 3. I'm not sure about his one, but it might make sense to add `camel-quarkus-support-httpclient` as a dependency to i.g. wiremock-support (maybe others), as some modules (like `integration-tests/xml`) depend on this module in runtime -- 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]
