[wildfly-dev] Jakarta EE 10, Some Platform TCK tests moving to new Standalone TCKs and impact on Platform TCK testing...

Hi, For Jakarta EE 10, we have six new Standalone SPEC level TCKs that will be required to be run by Jakarta EE 10 implementations like WildFly.  This email is to notify all interested in being involved in the discussion about how duplicate Platform TCK tests can be removed from the Platform TCK.  The discussion in [1] is the most active now, so that is a good issue to look at first whether you are interested in JSON Binding or only other SPECs. [2][3][4][5] are the pull requests for removing duplicate Platform TCK tests for other SPEC APIs.  [6] is the tracking issue for removing duplicate Platform TCK tests for Server Faces  since there is no pull request created yet. I think that it is important for the various (duplicate) SPEC API signature tests to remain in the Platform TCK, so that the SPEC APIs are validated on the various required EE containers.  Please comment on the issues with your feedback, discussion is also welcome here. Scott [1] Jakarta JSON Binding TCK https://github.com/eclipse-ee4j/jakartaee-tck/pull/848 + https://github.com/eclipse-ee4j/jakartaee-tck/pull/849 [2] Jakarta JSON Processing TCK https://github.com/eclipse-ee4j/jakartaee-tck/pull/842 [3] Jakarta Concurrency TCK https://github.com/eclipse-ee4j/jakartaee-tck/pull/816 [4] Jakarta BATCH TCK https://github.com/eclipse-ee4j/jakartaee-tck/pull/809 [5] Jakarta RESTful Web Services https://github.com/eclipse-ee4j/jakartaee-tck/pull/830 [6] Jakarta Server Faces TCK https://github.com/eclipse-ee4j/jakartaee-tck/issues/865