On Fri, Oct 30, 2015 at 11:16 PM, Steve Loughran <ste...@hortonworks.com> wrote: > >> On 29 Oct 2015, at 15:40, Tsuyoshi Ozawa <oz...@apache.org> wrote: >> >> Steve, >> >>> If you exclude jax-rs 2 and try to stay @ jersey 1.9 for your client, all >>> the http clients: KMS, webhdfs, ATS, aren't going to link. >> >> I thought we can use Jersey 1.19 on JDK 8 with client-side >> compatibility, but do you mean that we cannot use Jersey 1.19 on JDK >> 8? Please correct me if I've misunderstood. >> > > jersey 1.19 works on JDK8. What I'm worried about is having two versions of > jersey on the classpath -as the patch you've put up rewrites all the > client-side code to move to jersey 2 >
A latest patch I updated(HADOOP-9613.007.incompatible.patch) uses Jersey 1.19. All rewrites at client-side code I updated is to avoid using deprecated method, ClientResponse.getClientResponseStatus(). In fact, we can still use the method though it's marked as deprecated since 1.18. https://jersey.java.net/nonav/apidocs/1.19/jersey/com/sun/jersey/api/client/ClientResponse.html https://jersey.java.net/nonav/apidocs/1.19/jersey/com/sun/jersey/api/client/ClientResponse.html#getClientResponseStatus() Maybe the latest patch confuses you with non-essential change. I'm sorry for that. Please correct me if I'm wrong. Best, - Tsuyoshi
