Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-7996

Jakarta EE TCKs and compatibility

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.4.7
    • 3.4.8
    • 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

      [6]
      https://github.com/eclipse-ee4j/jakartaee-tck/wiki/Instructions-for-building-and-running-JakartaEE-TCK-bundle

      [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 

      Attachments

        1. JTreport-26-December-2019.zip
          130 kB
          Andriy Redko
        2. JTwork- 26-December-2019.zip
          6.38 MB
          Andriy Redko
        3. JTreport-11-January-2020.zip
          129 kB
          Andriy Redko
        4. JTwork-11-January-2020.zip
          6.36 MB
          Andriy Redko

        Issue Links

        There are no Sub-Tasks for this issue.

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            reta Andriy Redko
            reta Andriy Redko
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 0.5h
                0.5h

                Slack

                  Issue deployment