New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[quarkus-main]crypto test failure in native mode #3402
Comments
Verified this is the bouncycastle version mismatch between camel/camel-quarkus/quarkus. |
…ld failure in crypto
…ld failure in crypto
the commit has been squashed in quarkus-main : cf . 3c125ca And I pushed this fix: #3412 I'm not sure on which branch this was happening for you ? And right now I'm still syncing quarkus-main and camel-main, working on failures since updating to latest main. FYI, the bouncycastle.version is upgraded automatically when we do |
Thanks @zbendhiba! And I ran into this conflict on quarkus-main branch(quarkus upgraded to use bouncycastle 1.70 very recently) Actually I found more CQ components are affected by this because they still depend on BC 1.69 pulsar, and we need change like
and tika, we need change like
Also we need to add bcmail-jdk15on and bcutil-jdk15on to the dependency management
to get it work again |
Seems there's now a new error:
https://github.com/apache/camel-quarkus/runs/4771122780?check_suite_focus=true |
@jamesnetherton hmm, somehow I can't reproduce this locally on quarkus-main branch(No this error with both JDK11 and JDK17 ) |
Hmm the problem seems to pop up at random. Sometimes the native itests work fine. Other times it complains that the provider was not registered.... |
Issues seem to be resolved now. |
This happens on both JDK17 and JDK11. Probably is caused by camel-crypto and quarkus now use different bouncycastle version(1.69 VS 1.70)
The text was updated successfully, but these errors were encountered: