I'd stick with what you currently have working. However, I would use this
as a stick to push your organization to upgrade. 1.6 is really old.
On Mon, Mar 17, 2014 at 9:47 AM, Trolly Rogers <trolly.s.rogers_at_gmail.com>wrote:
> Ouch, that's disappointing.
>
> So users ...what would you do? Stick with 2.6 until my big slow
> organization upgrades our JVMs to 1.7, or remain in the dark ages with
> jaxrs 1.x knowing I'll at least get some critical patches if needed. Dang,
> this sucks!
>
>
> On Mon, Mar 17, 2014 at 12:23 PM, Noah White <emailnbw_at_gmail.com> wrote:
>
>> Works for me.
>>
>> -Noah
>>
>> On Mar 17, 2014, at 12:04 PM, cowwoc <cowwoc_at_bbs.darktech.org> wrote:
>>
>> > That seems to be a broken link. It redirects to
>> https://home.java.net/?force=689
>> >
>> > Gili
>> >
>> > On 17/03/2014 9:47 AM, Vetle Leinonen-Roeim wrote:
>> >> Seems like Java SE 7 is required now, just saw this pop up on the
>> jersey-commits mailing list:
>> https://java.net/projects/jersey/lists/commits/archive/2014-03/message/109
>> >>
>> >> On 15.03.14 01:15, Trolly Rogers wrote:
>> >>> Folks - Jersey documentation regarding java SE compatibility says "All
>> >>> Jersey components are compiled with Java SE 6 target.", but that's not
>> >>> the case with this latest 2.7 release. A number of components have
>> >>> manifest files that say Build-Jdk: 1.7.0_51, and of course it bombs
>> out
>> >>> on my 1.6 containers.
>> >>>
>> >>> Are going to get a jdk 1.6 build? (pretty please)
>> >>>
>> >>>
>> >>> Also, after swapping out jackson for moxy for my json stuff, my server
>> >>> startups got MUCH slower, anyone experience this?
>> >>
>> >
>>
>>
>