You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Andriy Redko (Jira)" <ji...@apache.org> on 2019/10/17 01:09:00 UTC
[jira] [Updated] (CXF-7996) Jakarta EE TCKs and compatibility
[ https://issues.apache.org/jira/browse/CXF-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andriy Redko updated CXF-7996:
------------------------------
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:
* {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]+
was:
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:
* {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}[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]+
> 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
>
> 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:
> * {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)