Repository navigation
Replies: 1 comment
I think this version of resteasy is being used for compatibility with undertow. If you have chance can you see if upgrading to 7.x would also require upgrading undertow? As long as all the arquillian tests pass that should be fine. Also have you tried just using a managed dependency for the resteasy-client version - I don't believe there will be any problems if you switch to 7.x for your usage of the admin client. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
For example,
keycloak-admin-client:26.0.8has the following transitive dependency chain:Libraries that have already migrated to the relocated artifact, such as Hibernate 6, require
io.smallrye:jandex:3.x, the successor oforg.jboss:jandex. Both artifacts share the same Java packages (org.jboss.jandex.*) but have different Maven coordinates, so dependency resolution does not deduplicate them. Both end up on the classpath simultaneously.The JVM classloader loads whichever JAR appears first. If
org.jboss:jandex 2.xis loaded first, this causes errors such asNoSuchMethodErrorfor methods that exist in3.xbut not in2.xWhile globally excluding
org.jboss:jandexin the consuming project's build configuration is a possible workaround, I would suggest considering an upgrade ofresteasy-clientto7.x, which already depends onio.smallrye:jandex:3.x. This would resolve the conflict transparently for all consumers.All reactions