Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.4.7
-
None
-
None
-
Unknown
Description
Mail thread: https://mail-archives.apache.org/mod_mbox/cxf-dev/201901.mbox/%3C6edd1da6-d651-
e2a3-8092-59bdc7a54ed4@apache.org%3E
Jakarta EE TCK: https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck
Github Repo: https://github.com/eclipse-ee4j/jakartaee-tck
Latest updates from [jakarta.ee-spec] TCK information, June 2019, the excerpts:
- We have summed up some information about how the TCK can be built (or
grabbed pre-built), configured, and run [1]. - This is assumed to be run against a Glassfish with the latest API
integrated (replacing the original API in the Glassfish).
- We have created a recording of a presentation of the Jenkins jobs that
manage all that [2].
- We have created 3 Jenkins files for pipeline job (as an example for
JSON-B TCK) to a) properly set the ts.jte configuration file, b) to grab
the API artifact built by a Jenkins build job and integrate it to a
Glassfish and c) to grab the pre-built TCK bundle from Eclipse Download,
grab the configured ts.jte file, grab the Glassfish with new API
integrated, and run the TCK [3].
For the complete information, please allow me to mention the list of the
TCK tasks needed to be done before the Jakarta EE release can be
finished [4].
The [5] is the example how to run Jakarta EE TCKs with Tomcat.
The [6] is the official list of the instructions.
The [7] is the list of the instructions from TomEE TCK .
[1] https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run
[2] https://youtu.be/nnD1KMvh0to
[3]
https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines
[4] https://github.com/orgs/eclipse-ee4j/projects/14
[5] https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs
[7] https://github.com/apache/tomee-tck
Summary:
- job location: https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/60/console
- the Jenkins pipeline and TCK configuration: https://github.com/apache/cxf/tree/master/tck
- the builds are against JakartaEE TCK master branch
- the JAX-RS TCK is build first
- than all JAX-RS tests are run against this JAX-RS TCK