Jetty/Jersey version conflicts

[rajim17]

Hi
We are using schema registry client in our rest service and we are facing version conflict with Jetty+Jersey packages.

rest-utils : Jetty (version : 8.1.16.v20140903) and Jersey ( version : 2.6)
our rest service : Jetty (version : 9.2.0.v20140526) and Jersey ( version : 2.9)
But we have to use Jersey 2.9 version for binders in our project.

As rest-utils brings Jetty 8.x version and it depends 2.6 version which breaks our rest service.

I see in latest rest-utils 2.0 snapshot jetty version is upgraded to 9.x. May I know when this would be released ? So we can use 2.x version of rest-utils.

Thanks
Raji

[miguno]

The planned release of rest-utils 2.0 is in December.

Until then you can also try jar-shading to resolve the version conflict:
https://maven.apache.org/plugins/maven-shade-plugin/
http://stackoverflow.com/questions/13620281

[ewencp]

Raji Muthupandian (@rajim17) Are you just using the kafka-schema-registry-client artifact or something more than that? The client code doesn't depend on rest-utils, jetty, jersey, etc. Its only dependencies are Avro, Jackson, and slf4j-log4j. This holds for the serializer artifact as well, which uses the client jar and we don't want to have any unnecessary dependencies since it is included in a wide variety of projects.

[rajim17]

I'm using kafka-schema-registry(which brings rest-utils) for my test cases. To test my client code, I need to bring up schema registry server locally.

[ewencp]

Raji Muthupandian (@rajim17) We've release v2.0.0 of Confluent Platform, which includes updated versions of Jetty and Jersey. Since we've changed the requirement to Java 7, we can now use newer versions of these libraries.

Does this now resolve the issue you were having? The versions are not exactly the same as you mention that you are using, but should be closer (in particular Jetty, which is now on the same major version, and is where I am guessing you were finding incompatibilities that jar-shading may not have resolved)?

Regardless, you may want to take care in writing unit tests using all of these services if you are not already depending on the particular versions as this is susceptible to similar conflicts in the future (whether due to your project changing versions or rest-utils/schema-registry changing versions).

[rajim17]

Thanks Ewen Cheslack-Postava (@ewencp) . I have started integrating with 2.0.0.
Hope this would solve the problem. Same major version of jetty would be fine. As restutils class is retired , working on changing to restservice.java. will let you know soon.

[ryan-barker-zefr]

Resolved the underlying issue in confluentinc/common and fixed a few changes in the code to make it work with the new versions

#93
confluentinc/common-docker#12
confluentinc/common#117

[ryan-barker-zefr]

Fixes #26