RE: Java 17 it’s my understanding that implementations can certify on Java 17 ONLY now with Jakarta EE 10? So I’m not sure what the issue is for Java 17?
Steve
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
On Behalf Of Ivar Grimstad
Sent: 06 October 2022 17:15
To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] Jakarta 10.1?
Hi Mark,
Discussions are ongoing. I think we can safely say that it will be at least Java SE 17 for Jakarta EE 11.
One of the reasons that came up for the 10.1 suggestion is also to make the transition to newer Java versions easier for developers. Possibly also opening up for raising the level to Java SE 21 for EE 11.
But this is very speculative and only suggestions so far. Stay tuned, and please do chime in with your views.
Is there agreement that Jakarta EE 11 will remove the SecurityManager
and require 17 as a minimum?
Mark
On 06/10/2022 17:02, Steve Millidge (Payara) wrote:
> It could be useful as an internal milestone for the TCK. However I don't see the benefit of releasing externally as it is more restrictive than Jakarta EE 10, so is not really a minor release and therefore could be confusing to consumers of Jakarta EE.
>
> Steve
>
>
> -----Original Message-----
> From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Reza Rahman
> Sent: 06 October 2022 16:55
> To: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
> Subject: Re: [jakartaee-platform-dev] Jakarta 10.1?
>
> I think this is a good idea. Java SE 17 needs to be dealt with sooner or later anyway. This will also provide an impression of a fresh and relevant platform.
>
> On 10/6/2022 11:38 AM, arjan tijms wrote:
>> Hi,
>>
>> In a similar vein to how we did Jakarta 9.1, what about doing a
>> Jakarta 10.1 that only focuses on the security manager removal and JDK 17?
>>
>> Jakarta 10.1 would then make sure that all TCKs are updated to not use
>> the security manager in any way, and subsequently only JDK 17 is
>> tested. Implementations certifying for Jakarta 10.1 are therefore
>> guaranteed to run without a security manager and are also guaranteed
>> to run at least on JDK 17.
>>
>> The work for Jakarta EE 11, which mainly takes place in the component
>> specification projects, can largely or even entirely continue in parallel.
>>
>> Thoughts?
>>
>> Kind regards,
>> Arjan Tijms
>>
>> _______________________________________________
>> jakartaee-platform-dev mailing list
>> jakartaee-platform-dev@xxxxxxxxxxx
>> To unsubscribe from this list, visit
>>
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
> _______________________________________________
> jakartaee-platform-dev mailing list
> jakartaee-platform-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
--
Ivar Grimstad
Jakarta EE Developer Advocate |
Eclipse Foundation
Eclipse Foundation - Community. Code.
Collaboration.
|
