Eureka Client dependency conflict Jersey 1.x / Jersey 2.x

[cforce]

We have to add the spring-boot-starter-jersey to put Jersyey 2.14 on the classpath. The mix of both versions lead to strange NoSuchMethodErrors during application startup! The only solution seems to be to use JAX-RX 1.x (Jersey 1) . How to deal with that?

Netflix/eureka#600 (comment)

[spencergibb]

If netflix is not planning on doing anything, there's not much we can do.

[foo4u]

Not sure what the issue with upgrading to javax.ws.rs 2.0.1. Why stick with the very outdated javax.ws.rs:jsr311-api:1.1.1?

[spencergibb]

We don't control the dependency, it's a Netflix/eureka issue. They don't plan on upgrading in the near term.

[spencergibb]

Now that I made my last comment, looks like things are changing! See this comment from the netflix team.

[foo4u]

Hi @spencergibb yes, I asked them directly about this. Good news. Let's keep an eye for that to hit master. 👍

[cforce]

Yes, hope it happens soon too

[spencergibb]

I'm going to close this. We track eureka changes regularly. We'll get the changes when they come. Though we won't be implementing a client api in jersey 2, we would wait for netflix or the community to add that.