On Fri, Oct 30, 2015 at 11:16 PM, Steve Loughran wrote:
>
>> On 29 Oct 2015, at 15:40, Tsuyoshi Ozawa 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 Jer
> On 29 Oct 2015, at 15:40, Tsuyoshi Ozawa 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
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
as an update, this looks like a "protbuf-class" incompatibility
the problem here is that this updates to JAX-RS 2.0, which is incompatible at
the client API
https://jersey.java.net/nonav/documentation/2.0/migration.html
which means everything downstream gets to rewrite their Jersey client code.
> I assume you are targetting this only at trunk / 3.0 based on the "target
> version" and the incompatibility discussion?
Yes, you're right.
Best regards,
- Tsuyoshi
On Tue, Oct 27, 2015 at 5:12 AM, Colin P. McCabe wrote:
> Looks like a good idea. I assume you are targetting this only at tr
Looks like a good idea. I assume you are targetting this only at trunk /
3.0 based on the "target version" and the incompatibility discussion?
best,
Colin
On Mon, Oct 26, 2015 at 7:07 AM, Tsuyoshi Ozawa wrote:
> Hi Steve,
>
> Thanks for your help.
>
> > 2. it's "significant"
>
> This change in
Hi Steve,
Thanks for your help.
> 2. it's "significant"
This change includes upgrading not only Jersey, but also its
dependencies like grizzly, asm, and so on.
> I'll try to rebuild a YARN app (slider) with the patch to see how it fares
It helps us a lot. I'd like to suggest that the incompat
https://issues.apache.org/jira/browse/HADOOP-9613 covers the issue of updating
Jersey to 3.0 to cope with the move to Java 8
1. this is trunk
2. it's "significant"
we've been frozen on an old version of Jersey with issues, known ones needing
separate threads to detect jersey startup failures,
