Given that the end of public updates for Java 6 was February 2013, it is
not surprising that Jersey is no longer supporting it.
Regards,
Mark Thornton
On Monday, 17 March 2014, Trolly Rogers <trolly.s.rogers_at_gmail.com> wrote:
> For some reason that link isn't working for me. Would you be able to paste
> or give me some more details?
>
> I was really hoping the SE 7 requirement was an oversight. I really want
> to upgrade to the latest Jersey, but unfortunately my organization won't be
> upgrading our servers for a while.
>
> So Jersey folks, are you done with 1.6? I gotta figure out a path forward
> here.... if I stick with Jersey 2.6 I figure I'll get screwed out of any
> updates presuming they'll all be built on 1.7. Alternatively, I can port my
> app back to Jersey 1.x. It's like a lose lose situation for me here unless
> Jersey 2 supports 1.6.
>
>
> On Mon, Mar 17, 2014 at 9:47 AM, Vetle Leinonen-Roeim <vetle_at_roeim.net<javascript:_e(%7B%7D,'cvml','vetle_at_roeim.net');>
> > 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?
>>>
>>
>>
>