|[jakarta.ee-spec] Process for TCK service releases that include TCK updates for running signature tests on newer JDK versions...|
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  for
updating signature tests).
Last December, we started making changes to the `TCK Process 1.0`
that includes the following text  which allows challenged +
accepted TCK failures to be present in a TCK compatibility
`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 )? 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  to be officially released by Spec team so that implementations can submit certification requests against jakarta-xml-binding-tck-3.0.2.zip).
Back to the top