Thanks for the feedback all. I'm doing my best to push for a 1.7 jvm, and
if I had it my way it would be a 1.8 container. Unfortunately the team
responsible for managing test/production runtime environments are MUCH
slower to adopt.
On Wed, Mar 19, 2014 at 9:42 AM, Marek Potociar
<marek.potociar_at_oracle.com>wrote:
> A minor correction:
>
> Jersey 2.7 and higher does not support Java SE 6 for server-side and all
> the extensions. The core client module will still be maintained to run on
> Java SE 6. We do not want to be too strict about client runtime, but we
> really believe that with Java SE 6 being EOLed, server-side runtime has to
> move to Java SE 7 or higher.
>
> Marek
>
> P.S. We clearly didn't do a great job of giving heads-up to the community
> about our decision to move to Java SE 7. The lesson has been learned. Once
> we decide to switch also the remaining core common & client modules, we
> will make sure to do a better job of letting you know in advance to avoid
> surprises.
>
>
> On 17 Mar 2014, at 19:33, Mark Thornton <mthornton_at_optrak.com> wrote:
>
> 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>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?
>>>>
>>>
>>>
>>
>