[
https://issues.apache.org/jira/browse/CXF-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004584#comment-17004584
]
Andriy Redko commented on CXF-7996:
-----------------------------------
Hey [~deki] , thanks a lot for offering help. Basically, there are 4 steps
involved:
1) Fork [https://github.com/eclipse-ee4j/jakartaee-tck]
2) Fetch Glassfish 5.1.0 distribution from Maven repository and unpack it (it
is not strictly necessary but TCK needs some APIs like CDI, Bean Validation,
... to compile which come with Glassfish already).
3) Build JAX-RS TCK with custom config file (I have it, templating it so we
could parametrize it with CXF version)
4) Run JAX-RS TCK tests with custom config file (basically, start Glassfish,
deploy all WARs and run tests)
Probably, one thing we may run into right away is a need to dynamically
configure Glassfish port in order to avoid port conflicts. I think I have
enough permissions to create custom jobs on Jenkins, so I could start and ask
for your help guys.
Thanks!
> Jakarta EE TCKs and compatibility
> ---------------------------------
>
> Key: CXF-7996
> URL: https://issues.apache.org/jira/browse/CXF-7996
> Project: CXF
> Issue Type: Task
> Reporter: Andriy Redko
> Assignee: Andriy Redko
> Priority: Major
> Attachments: JTreport-26-December-2019.zip, JTwork-
> 26-December-2019.zip
>
>
> Mail thread:
> [https://mail-archives.apache.org/mod_mbox/cxf-dev/201901.mbox/%3C6edd1da6-d651-]
> e2a3-8092-59bdc7a54...@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:
> * {color:#000000}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#000000}grabbed pre-built), configured, and run [1].{color}
> * {color:#000000}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#000000}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#000000}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#000000}manage all that [2].{color}
> * {color:#000000}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#000000}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#000000}the API artifact built by a Jenkins build job and integrate
> it to a {color}
> {color:#000000}Glassfish and c) to grab the pre-built TCK bundle from
> Eclipse Download, {color}
> {color:#000000}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#000000}integrated, and run the TCK [3].{color}
> {color:#000000}For the complete information, please allow me to mention the
> list of the {color}
> {color:#000000}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#000000}finished [4].{color}
> {color:#000000}The [5] is the example how to run Jakarta EE TCKs with
> Tomcat.{color}
> {color:#000000}{color:#000000}The{color} [6] is the official list of the
> instructions.{color}
>
> {color:#000000}[1]
> {color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#000000}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#000000}[3] {color}
>
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#000000}[4] {color}+[https://github.com/orgs/eclipse-ee4j/projects/14]+
> [5] [https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs]
> [6]
> +[https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Instructions-for-building-and-running-JakartaEE-TCK-bundle]+
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
