Re: [jakartaee-platform-dev] [ejb-dev] [External] : Please giveyour esti

[<Hussain.NM@xxxxxxxxxxxxx>]

FYI, TCK team is running 9.1 against JDK8 with Glassfish 6.0.

https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Jakarta-EE-9.1-TCK-results#full-platform-tck-results-with-jdk8

Thanks
Hussain

-----Original Message-----
From: jakartaee-platform-dev <jakartaee-platform-dev-bounces@xxxxxxxxxxx> On Behalf Of David Blevins
Sent: Saturday, March 20, 2021 12:26 AM
To: Ed Bratt <ed.bratt@xxxxxxxxxx>
Cc: jakartaee-platform developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Re: [jakartaee-platform-dev] [ejb-dev] [External] : Please giveyour estimate of when you will complete your tasks for Jakarta EE 9.1 TCKs...


> On Mar 19, 2021, at 11:43 AM, Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:
>
> A couple of points -- I hope these clarify --
>
> 1) there is no stand-alone TCK for Jakarta Enterprise Beans. If Enterprise Beans TCK changes, the Jakarta EE Platform TCK (a.k.a. CTS) is updated and a new version is required. This is true for any Spec. that doesn't have a stand-alone TCK (Platform, Web Profile, Enterprise Beans, Enterprise Web Services, Interceptors, Managed Beans, Web Services Metadata).
>
> 2) if a TCK released in 9.0 passes both JDK 11 and JDK 8 without change, it doesn't need to be re-released but a compatible implementation must submit a compatibility certification issue showing JDK 11.
>
> 3) Any TCK that must be rebuilt, even if there wasn't believed to be a required change must be released again -- if for no other reason, the SHA sums will no longer match.
>
> (Clarifying 2 above) Since there was no Compatible Implementation requirement for component implementations to pass JDK 11 with the 9.0 release, all specifications must verify their TCK against a compatible implementation before we can claim those components meet the requirement of working on JDK11. So, at the least, Compatible Implementation issues for each spec. will be needed -- even if the TCK isn't updated.
>
> One more reminder, compatible products must add Jakarta XML Binding TCK results for platforms, when certifying with JDK 11 or higher (along with their results for DI, CDI and Bean Validation).

Agree.   Adding two important items as long as we're making a list:

4) If we are updating signature files for a component spec, we should do a service release of that component spec assuming it does have a standalone TCK.  Jakarta Enterprise Beans does not, so the javax.rmi.PortableRemoteObject signature tests we're adding do not require a service release.

5) We do need to verify that the Jakarta EE 9.1 TCK can be passed on JDK 8.  Results on JDK 8 for the Jakarta EE 9.0 TCK do not eliminate this need.


-David

_______________________________________________

This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.