TCK challenge for adding support for running Security 3.0 signature TCK tests on Java 21 #297
Comments
|
Since all of the Signature test failures also happen in the Platform TCK signature tests we can probably address that first and likely make the same one line change in other places as well. I think we should turn these issues into TCK challenges so could one of the contributors please add the |
scottmarlow
changed the title
scottmarlow
changed the title
|
I can confirm that the jakartaee/platform-tck#1206 change solved ^ running the (Jakarta EE 10) Platform TCK Signature tests on Java 21 and the same change should help the Security TCK. |
^ is done and the updated Platform TCK 10.0.3 TCK is released as mentioned on https://jakarta.ee/specifications/platform/10 |
|
Could one of the Security project committers please add the |
arjantijms
added
challenge
|
@scottmarlow sorry for the delay. Of course this will be done for the final release of the TCK. I just did the same for the Jakarta Authorization TCK. See: https://github.com/jakartaee/authorization/tree/master/tck/authorization-signaturetest |
@arjantijms to be clear, I think that we need a https://www.eclipse.org/downloads/download.php?file=/jakartaee/security/3.0/jakarta-security-tck-3.0.2.zip release that includes the #305 fix as well. |
|
@scottmarlow okay, that should be doable |
|
I've staged 3.0.2 here, but not checked it yet: |
Thanks, I'm working on running it locally with latest WildFly on Java 17 and will then run again on Java 21. |
|
The JDK 21 run against GlassFish 7.0.15 succeeded: https://ci.eclipse.org/jakartaee-tck/view/EFTL-Certification-Jobs-10/job/10/job/jakarta-security-tck-glassfish/141/ |
|
I'm hitting environmental problems locally so probably a good idea to promote it as I did at least see the signature tests pass locally with JDK21:
|
|
JDK 11 and JDK 17 runs passed too. I'll ask for the promotion. |
|
@arjantijms any idea why Apache Tomcat might be used for some tests by default? I previously tested with the 3.0.0 TCK but not 3.0.1 (in case that helps). https://gist.github.com/scottmarlow/50802d6a60ca5228fa92d207b4d44a78 shows some evidence of I also saw the first 3.0.2 TCK test failure with error |
|
Perhaps ^ problem with Tomcat automatically starting for some tests is related to the #284 change for 3.0.1. |
Yes, two tests use an OpenID Connect Server to test against, and this just happens to be a Tomcat application. It's similar to how e.g. the Jakarta Mail TCK starts up a Mail Server to test against. |
When running the https://www.eclipse.org/downloads/download.php?file=/jakartaee/security/3.0/jakarta-security-tck-3.0.1.zip tests on Java 21, the following signature test failures occur due to Java 21 added a few new JDK methods:
There are two possible fixes, the easiest one line change would be to exclude the specific updated JDK classes on the command line when invoking the sigtest tool. I'll look into that next year.
The better change would be to update https://github.com/jtulach/netbeans-apitest to be able to avoid checking any SPEC API classes that are not in the
jakartanamespace which I think would avoid validation of any JDK classes and instead focus only on checkingjakarta.*classes. I'd like to do this change for Jakarta EE 11+.The text was updated successfully, but these errors were encountered: