You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
java.lang.RuntimeException: java.lang.NoSuchMethodError: 'void okhttp3.internal.Internal.initializeInstanceForTests()'
at io.quarkus.test.junit.QuarkusTestExtension.throwBootFailureException(QuarkusTestExtension.java:638)
at io.quarkus.test.junit.QuarkusTestExtension.interceptTestClassConstructor(QuarkusTestExtension.java:722)
at java.base/java.util.Optional.orElseGet(Optional.java:364)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: java.lang.NoSuchMethodError: 'void okhttp3.internal.Internal.initializeInstanceForTests()'
at okhttp3.mockwebserver.MockWebServer.<clinit>(MockWebServer.java:103)
The text was updated successfully, but these errors were encountered:
jamesnetherton
changed the title
kubernetes: testKubernetesComponent is failing on the platform
kubernetes: testKubernetesComponent is failing on the quarkus-platform
Feb 27, 2024
No, I don't think so. While mockwebserver is not in our BOM and the k8s client still aligns with okhttp 3.x, the dependency tree ends up being a mess when tests run because IIRC the universe BOM is used:
Bug description
While releasing Camel Quarkus 3.8.0, test below was failing:
The text was updated successfully, but these errors were encountered: