| Re: [jakarta.ee-spec.committee] Fwd: Process for TCK service releases that include TCK updates for running signature tests on newer JDK versions... |
_______________________________________________Switching to jakarta.ee-spec.committee@xxxxxxxxxxx which might be a better email for this. I hadn't really noticed the distinction between this private email list versus jakarta.ee-spec@xxxxxxxxxxx before.
As per what we discussed last year, I added the following text to the `tckprocess` document [2] for which I think we can take action for EE 10 (once the pr [2] is merged):
"Excluded tests should be added back in for every major Jakarta EE release by emptying the test exclude list for every Specification developed in the respective major EE release."
As per the use of the word "should", I think the intention is to encourage each Spec and the various implementation teams to correct the excluded tests so that the tests can be enabled for the Jakarta EE 10 release (during the development of EE 10). Agreed?
Also, does the [2] pr simply need more than a single approver?
Scott
-------- Forwarded Message --------
Subject: Process for TCK service releases that include TCK updates for running signature tests on newer JDK versions... Date: Tue, 3 Aug 2021 09:54:04 -0400 From: Scott Marlow <smarlow@xxxxxxxxxx> To: jakarta.ee-spec@xxxxxxxxxxx
Hello,
For Jakarta EE Platform 9.1+, the Platform Spec supports implementations running TCK compatibility certification tests on JDK versions Java SE 8, Java SE 11+. In support of running TCK tests on JDK versions greater than SE 11, we expect that some tests will need to be revised (e.g. see jaxb-tck/issues/57 [1] for updating signature tests).
Last December, we started making changes to the `TCK Process 1.0` that includes the following text [2] which allows challenged + accepted TCK failures to be present in a TCK compatibility certification request:
`The specification project may approve (user) workarounds for an `accepted` TCK challenge (as alternative to excluding TCK tests).`
My question today is whether the above quoted text is enough to cover Jakarta EE 9.1 compatibility certification requests against Java SE 17 (which will include signature test failures due to jaxb-tck/issues/57 [1])? If the answer/vote is yes, signature test failures can be ignored on newer JDK versions, if and only if the signature test failure is caused by inadequate TCK signature support for the relevant Java SE version. If the answer/vote is no, we will need an additional TCK process change to specifically allow a SPEC TCK service release that updates signature tests to resolve the signature test failure (e.g. allow jakarta-xml-binding-tck-3.0.2.zip [4] to be officially released by Spec team so that implementations can submit certification requests against jakarta-xml-binding-tck-3.0.2.zip).
Scott
[1] https://github.com/eclipse-ee4j/jaxb-tck/issues/57
[2] https://github.com/jakartaee/jakarta.ee/pull/1018/files#diff-1fe254a18287c0db31fd9cb0a6bca11b1efda926095c3a65b73ef2ae0c89360dR223
[3] https://jakarta.ee/committees/specification/tckprocess/
[4] https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee9-eftl/promoted/jakarta-xml-binding-tck-3.0.2.zip
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee