updating dropwizard to 2.0.13 causes issues with jersey abstractBinder (using <artifactId>dropwizard-bom</artifactId>) #4769
Replies: 9 comments
-
Jersey 2.25.1 and Jetty 9.4.18.v20190429 are not the versions of these dependencies provided by Dropwizard 2.0.13 but look like they came from Dropwizard 1.3.x. You're probably overriding them somewhere in your build. |
Beta Was this translation helpful? Give feedback.
-
Thanks for looking into this Jochen! |
Beta Was this translation helpful? Give feedback.
-
Please post the output of |
Beta Was this translation helpful? Give feedback.
-
@Ahmad-alsanie any follow up on your solution? I'm having similar issues. |
Beta Was this translation helpful? Give feedback.
-
@chidog12 Check the output of |
Beta Was this translation helpful? Give feedback.
-
@joschi I believe the issue exists when using:
unfortunately I cannot share effective pom due to some internal dependencies but I've analyzed it all. and the old versions of jetty and jersey are certainly coming from
I've updated my project not to use the bom to control the versions rather statically defined each of
there's certainly an issue here. |
Beta Was this translation helpful? Give feedback.
-
@Ahmad-alsanie Please read the upgrade notes for Dropwizard 2.0.x: |
Beta Was this translation helpful? Give feedback.
-
alright, that makes sense. let me check if I can use dependencies instead. Thank you very much! |
Beta Was this translation helpful? Give feedback.
-
using:
solved the issue. Thanks! |
Beta Was this translation helpful? Give feedback.
-
Getting
When I update my project to latest dropwizard. apparently there's a dependency issue here
mvn dependency:tree
:I've tried to explicitly add
jersey-client
andjersey-client
but that will cause:java.lang.NoSuchFieldError: INCLUDE_ALL
also adding jersey-bom won't workBeta Was this translation helpful? Give feedback.
All reactions