Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [External] : Release plan revisions to mitigate impact of gh-platform-820 and preserve June/July delivery of EE 11

I am confused as to why it is necessary to switch direction at this late stage and why this decision is being made in the platform project. The reason stated in the GitHub issue is about market adoption so I think the steering committee should be brought into the loop to provide a steer. The working group side of Jakarta EE is where market adoption concerns should be resolved.

I am assuming there is no technical reason why JDK 21 can't be the baseline as the given amendment to the release plan states that there will still be a shippable runtime running on JDK 21 therefore all Compatible Implementations must support Java 21? 

Actually having to support JDK 17 and JDK 21 in the TCKs and GlassFish project I assume is a lot of additional busy work. 

Steve Millidge
Founder & CEO Payara


-----Original Message-----
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of Lukas Jungmann via jakartaee-platform-dev
Sent: Tuesday, January 16, 2024 3:24 PM
To: Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>; jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Cc: Lukas Jungmann <lukas.jungmann@xxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] [External] : Release plan revisions to mitigate impact of gh-platform-820 and preserve June/July delivery of EE 11

On 16.01.2024 16:11, Ivar Grimstad wrote:
> I don't see any problems using the '--release 17' flag. That's what I 
> plan to do for MVC at least.

That is what most, if not all, projects I work on use as well. The thing is:

In some projects there is @snippet which came in javadoc in SE 18 being used, so if anyone tries to rebuild such project _with javadoc_ on SE 17, the build is going to fail, even though the javadoc is set to use '--release 17' as well.


--lukas


> 
> Ivar
> 
> On Tue, Jan 16, 2024 at 4:09 PM Lukas Jungmann via 
> jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx
> <mailto:jakartaee-platform-dev@xxxxxxxxxxx>> wrote:
> 
>     Hi,
> 
>     On 15.01.2024 20:18, Ed Burns via jakartaee-platform-dev wrote:
>      >       o *Component spec TCKs and platform TCK must compile under 17*.
> 
>     Does this mean that Java SE 17 must be used for build OR does this mean
>     that the compiler must be set to use '--release 17' flag?
> 
>     thanks,
>     --lukas
> 
> 
> 
>      >       o *A compatible component impl must pass their component
>     TCK when
>      >         run under 17 and also 21.*
>      >       o *A compatible platform impl must pass the platform TCK
>     when run
>      >         under 17 and also 21.*
>      >   * Platform project adjusts "release review" targets for component
>      >     specs: *move "release review" targets all out by one
>     month* relative
>      >     to the schedule sent to Spec Project Leads on 2023-12-13
>      >   
>       <https://urldefense.com/v3/__https://www.eclipse.org/lists/jakartaee-spec-project-leads/msg00851.html__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43An6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wKzzNC1g$ <https://urldefense.com/v3/__https://www.eclipse.org/lists/jakartaee-spec-project-leads/msg00851.html__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43An6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wKzzNC1g$>>.
>      >       o Wave 1, 2, 3, 4 specs release review by 2024-02-29
>      >       o M2 release
>      >       o Wave 5 specs release review by 2024-03-29
>      >       o M3 release
>      >       o Wave 6, 7 specs release review by 2024-04-27
>      >       o M4 release
>      >
>      >   * The key condition to make this plan possible: the GlassFish
>      >     community is willing and able to deliver an implementation of
>     EE 11
>      >     compiled under 17, but passing the platform TCK under 17 and also
>      >     21. *The release coordinators expect more community
>     involvement on
>      >     the Jakarta Data implementation for GlassFish, especially
>     from Red
>      >     Hat, to achieve this goal.*
>      >
>      > *Details*
>      >
>      > On 2023-12-20, Red Hat opened gh-platform-820
>      >
>     <https://urldefense.com/v3/__https://github.com/jakartaee/platform/issues/820__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43An6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wJXqlWNT$ <https://urldefense.com/v3/__https://github.com/jakartaee/platform/issues/820__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43An6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wJXqlWNT$>>. This issue requests, "there still must be support for Java SE 17 as a valid runtime for certification." We spent the 2024-01-09 platform project call discussing this issue. Since then, the release coordinators have been working to revise the release plan to accommodate this request, while preserving the delivery schedule and maintaining buy-in from implementation vendors.
>      >
>      > We believe the revised plan achieves this objective. We ask you
>     to read
>      > it and understand it carefully. If you think it's unachievable,
>     now is
>      > the best time to say it.
>      >
>      > We will discuss this tomorrow. We aim to modify the Jakarta EE 11
>      > Release Plan
>      >
>     <https://urldefense.com/v3/__https://jakartaee.github.io/platform/jakartaee11/JakartaEE11ReleasePlan__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43An6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wAYwAzzs$ <https://urldefense.com/v3/__https://jakartaee.github.io/platform/jakartaee11/JakartaEE11ReleasePlan__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43An6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wAYwAzzs$>> right after the meeting and convey the changes to the spec and steering committees.
>      >
>      > Thanks,
>      >
>      > Ed and Arjan
>      >
>      > P.S. The long-standing policy of considering specification
>     binaries, in
>      > maven central or anywhere else, as a non-normative convenience
>     remains
>      > unchanged. The platform project is silent on this matter. But
>     because
>      > the platform project *does* mandate a specific JDK requirement for
>      > compatible implementations passing the component or platform TCK,
>      > specification binaries are practically constrained to follow that
>     mandate.
>      >
>      > **
>      >
>      > | edburns@xxxxxxxxxxxxx <mailto:edburns@xxxxxxxxxxxxx>
>     <mailto:edburns@xxxxxxxxxxxxx <mailto:edburns@xxxxxxxxxxxxx>> |
>     office: +1 954
>      > 727 1095
>      >
>      > | Calendar Booking: https://aka.ms/meetedburns
>     <https://urldefense.com/v3/__https://aka.ms/meetedburns__;!!ACWV5N9M2RV99hQ!MQaB4_I5DrrOy-WXmDcIYMojeG6BKHZiaGNuggIV483K62bZkpkgAsfasDjgVXRdatFHVa2fnPEyEmz7RJUlAYbOvfLcmlAL3AiaJw$>
>      >
>     <https://urldefense.com/v3/__https://aka.ms/meetedburns__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43An6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wJzdIhRw$ <https://urldefense.com/v3/__https://aka.ms/meetedburns__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43An6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wJzdIhRw$>>
>      >
>      > |
>      >
>      > | Please don't feel obliged to read or reply to this e-mail outside
>      >
>      > | of your normal working hours.
>      >
>      > |
>      >
>      > | Reply anonymously to this email:
>      > https://purl.oclc.org/NET/edburns/contact
>     <https://urldefense.com/v3/__https://purl.oclc.org/NET/edburns/contact__;!!ACWV5N9M2RV99hQ!MQaB4_I5DrrOy-WXmDcIYMojeG6BKHZiaGNuggIV483K62bZkpkgAsfasDjgVXRdatFHVa2fnPEyEmz7RJUlAYbOvfLcmlADEWfp4Q$>
>      >
>     <https://urldefense.com/v3/__https://purl.oclc.org/NET/edburns/contact__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43An6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wJBHc8pU$ <https://urldefense.com/v3/__https://purl.oclc.org/NET/edburns/contact__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43An6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wJBHc8pU$>>
>      >
>      >
>      > _______________________________________________
>      > jakartaee-platform-dev mailing list
>      > jakartaee-platform-dev@xxxxxxxxxxx
>     <mailto:jakartaee-platform-dev@xxxxxxxxxxx>
>      > To unsubscribe from this list, visit
>     
> https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/j
> akartaee-platform-dev__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43An
> 6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wMyO0F-k$ 
> <https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/
> jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!PKorn7h1TiIZpFUJOb7mW2FA43A
> n6xf0yzgdJE79RdF-rNx8RQexSrZJ7xMP-SGb6ff7hNuesvvZ1Ha4Fmd6JSD0wMyO0F-k$
> >
> 
>     _______________________________________________
>     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://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/
> jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!MQaB4_I5DrrOy-WXmDcIYMojeG6
> BKHZiaGNuggIV483K62bZkpkgAsfasDjgVXRdatFHVa2fnPEyEmz7RJUlAYbOvfLcmlBPY
> _fopQ$>
> 
> 
> 
> --
> 
> Ivar Grimstad
> 
> Jakarta EE Developer Advocate | *Eclipse Foundation *Eclipse 
> Foundation
> <https://urldefense.com/v3/__https://www.eclipse.org/__;!!ACWV5N9M2RV99hQ!MQaB4_I5DrrOy-WXmDcIYMojeG6BKHZiaGNuggIV483K62bZkpkgAsfasDjgVXRdatFHVa2fnPEyEmz7RJUlAYbOvfLcmlC85LeUdw$>- 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

Back to the top