Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Jakarta 10.1?

I don’t see the value here either, and I don’t buy the argument that it would not have an impact on Jakarta EE 11. Originally Jakarta EE 10 was due in June and it was released in September and I’m sure Jakarta EE 9.1 was a part of that delay. If we want Jakarta EE 11 in a years time and to be on time I would think we should focus on that and not a Jakarta EE 10.1. It isn’t clear to me what the advantage to Jakarta EE would be, either from a user or an implementation perspective 

Alasdair

Alasdair Nottingham

> On Oct 6, 2022, at 12:45 PM, Mark Thomas <markt@xxxxxxxxxx> wrote:
> 
> On 06/10/2022 17:15, Ivar Grimstad wrote:
>> 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.
> 
> Personal view only.
> 
> I am hugely in favour of Jakarta EE 11:
> - requiring Java 17 as a minimum
> - removing all support for SecurityManager
> 
> I don't see much benefit in 10.1 as described so far. Given how much effort a release seems to require, I'd rather see that effort focused on 11.
> 
> Mark
> 
> 
>> Ivar
>> On Thu, Oct 6, 2022 at 6:11 PM Mark Thomas <markt@xxxxxxxxxx <mailto:markt@xxxxxxxxxx>> wrote:
>>    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
>>    <mailto: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
>>    <mailto: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
>>    <mailto:jakartaee-platform-dev@xxxxxxxxxxx>
>>     >> To unsubscribe from this list, visit
>>     >> https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
>>    <https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev>
>>     > _______________________________________________
>>     > jakartaee-platform-dev mailing list
>>     > jakartaee-platform-dev@xxxxxxxxxxx
>>    <mailto:jakartaee-platform-dev@xxxxxxxxxxx>
>>     > To unsubscribe from this list, visit
>>    https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
>>    <https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev>
>>     > _______________________________________________
>>     > jakartaee-platform-dev mailing list
>>     > jakartaee-platform-dev@xxxxxxxxxxx
>>    <mailto:jakartaee-platform-dev@xxxxxxxxxxx>
>>     > To unsubscribe from this list, visit
>>    https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
>>    <https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev>
>>    _______________________________________________
>>    jakartaee-platform-dev mailing list
>>    jakartaee-platform-dev@xxxxxxxxxxx
>>    <mailto:jakartaee-platform-dev@xxxxxxxxxxx>
>>    To unsubscribe from this list, visit
>>    https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
>>    <https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev>
>> -- 
>> Ivar Grimstad
>> Jakarta EE Developer Advocate | *Eclipse Foundation *Eclipse Foundation <https://www.eclipse.org/>- Community. Code. Collaboration.
>> _______________________________________________
>> 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


Back to the top