[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:
--
Affects Version/s: 3.4.7
> Jakarta EE TCKs and compatibility
> -
>
> Key: CXF-7996
> URL: https://issues.apache.org/jira/browse/CXF-7996
> Project: CXF
> Issue Type: Task
>Affects Versions: 3.4.7
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.8
>
> Attachments: JTreport-11-January-2020.zip,
> JTreport-26-December-2019.zip, JTwork- 26-December-2019.zip,
> JTwork-11-January-2020.zip
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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:#00}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#00}grabbed pre-built), configured, and run [1].{color}
> * {color:#00}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#00}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#00}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#00}manage all that [2].{color}
> * {color:#00}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#00}the API artifact built by a Jenkins build job and integrate
> it to a {color}
> {color:#00}Glassfish and c) to grab the pre-built TCK bundle from
> Eclipse Download, {color}
> {color:#00}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the
> list of the {color}
> {color:#00}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with
> Tomcat.{color}
> {color:#00}The{color} [6] is the official list of the instructions.
> {color:#00}The{color} [7] is the list of the instructions from TomEE TCK .
>
> [1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[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]+
> [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|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
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[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:
--
Fix Version/s: 3.4.8
> 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
> Fix For: 3.4.8
>
> Attachments: JTreport-11-January-2020.zip,
> JTreport-26-December-2019.zip, JTwork- 26-December-2019.zip,
> JTwork-11-January-2020.zip
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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:#00}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#00}grabbed pre-built), configured, and run [1].{color}
> * {color:#00}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#00}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#00}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#00}manage all that [2].{color}
> * {color:#00}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#00}the API artifact built by a Jenkins build job and integrate
> it to a {color}
> {color:#00}Glassfish and c) to grab the pre-built TCK bundle from
> Eclipse Download, {color}
> {color:#00}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the
> list of the {color}
> {color:#00}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with
> Tomcat.{color}
> {color:#00}The{color} [6] is the official list of the instructions.
> {color:#00}The{color} [7] is the list of the instructions from TomEE TCK .
>
> [1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[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]+
> [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|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
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[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-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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
b) to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new
API {color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can
be {color}
{color:#00}finished [4].{color}
{color:#00}The [5] is the example how to run Jakarta EE TCKs with
Tomcat.{color}
{color:#00}The{color} [6] is the official list of the instructions.
{color:#00}The{color} [7] is the list of the instructions from TomEE TCK .
[1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[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]+
[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|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
was:
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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
b) to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new
API {color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can
be {color}
{color:#00}finished [4].{color}
{color:#00}The [5] is the example how to run Jakarta EE TCKs with
Tomcat.{color}
{color:#00}The{color} [6] is the official list of the instructions.
[1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
[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-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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
b) to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new
API {color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can
be {color}
{color:#00}finished [4].{color}
{color:#00}The [5] is the example how to run Jakarta EE TCKs with
Tomcat.{color}
{color:#00}The{color} [6] is the official list of the instructions.
[1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[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]+
[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|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
was:
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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
b) to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new
API {color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can
be {color}
{color:#00}finished [4].{color}
{color:#00}The [5] is the example how to run Jakarta EE TCKs with
Tomcat.{color}
{color:#00}The{color} [6] is the official list of the instructions.
[1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[4]
[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-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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
b) to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new
API {color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can
be {color}
{color:#00}finished [4].{color}
{color:#00}The [5] is the example how to run Jakarta EE TCKs with
Tomcat.{color}
{color:#00}The{color} [6] is the official list of the instructions.
[1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[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]+
*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|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
was:
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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
b) to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new
API {color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can
be {color}
{color:#00}finished [4].{color}
{color:#00}The [5] is the example how to run Jakarta EE TCKs with
Tomcat.{color}
{color:#00}The{color} [6] is the official list of the instructions.
[1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[4]
[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-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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
b) to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new
API {color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can
be {color}
{color:#00}finished [4].{color}
{color:#00}The [5] is the example how to run Jakarta EE TCKs with
Tomcat.{color}
{color:#00}The{color} [6] is the official list of the instructions.
[1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[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]+
Summary:
- job location: *[https://builds.apache.org/view/C/view/Apache]
CXF/job/CXF-JAXRS-TCK/*
- the Jenkins pipeline and TCK configuration:
[https://github.com/apache/cxf/tree/master/tck|https://github.com/apache/cxf/tree/master/tck*]
was:
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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
b) to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new
API {color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can
be {color}
{color:#00}finished [4].{color}
{color:#00}The [5] is the example how to run Jakarta EE TCKs with
Tomcat.{color}
{color:#00}The{color} [6] is the official list of the instructions.
[1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[4] {color}+[https://github.com/orgs/eclipse-ee4j/projects/14]+
[5] [https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs]
[6]
[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-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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
b) to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new
API {color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can
be {color}
{color:#00}finished [4].{color}
{color:#00}The [5] is the example how to run Jakarta EE TCKs with
Tomcat.{color}
{color:#00}The{color} [6] is the official list of the instructions.
[1] +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[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]+
Summary:
- job location: *https://builds.apache.org/view/C/view/Apache
CXF/job/CXF-JAXRS-TCK/*
- Jenkins pipeline and TCK configuration:
*https://github.com/apache/cxf/tree/master/tck*
was:
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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
b) to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new
API {color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can
be {color}
{color:#00}finished [4].{color}
{color:#00}The [5] is the example how to run Jakarta EE TCKs with
Tomcat.{color}
{color:#00}{color:#00}The{color} [6] is the official list of the
instructions.{color}
{color:#00}[1]
{color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[4] {color}+[https://github.com/orgs/eclipse-ee4j/projects/14]+
[5] [https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs]
[6]
[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:
--
Attachment: JTreport-11-January-2020.zip
> 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-11-January-2020.zip,
> JTreport-26-December-2019.zip, JTwork- 26-December-2019.zip,
> JTwork-11-January-2020.zip
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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:#00}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#00}grabbed pre-built), configured, and run [1].{color}
> * {color:#00}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#00}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#00}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#00}manage all that [2].{color}
> * {color:#00}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#00}the API artifact built by a Jenkins build job and integrate
> it to a {color}
> {color:#00}Glassfish and c) to grab the pre-built TCK bundle from
> Eclipse Download, {color}
> {color:#00}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the
> list of the {color}
> {color:#00}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with
> Tomcat.{color}
> {color:#00}{color:#00}The{color} [6] is the official list of the
> instructions.{color}
>
> {color:#00}[1]
> {color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[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)
[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:
--
Attachment: JTwork-11-January-2020.zip
> 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-11-January-2020.zip,
> JTreport-26-December-2019.zip, JTwork- 26-December-2019.zip,
> JTwork-11-January-2020.zip
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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:#00}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#00}grabbed pre-built), configured, and run [1].{color}
> * {color:#00}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#00}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#00}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#00}manage all that [2].{color}
> * {color:#00}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#00}the API artifact built by a Jenkins build job and integrate
> it to a {color}
> {color:#00}Glassfish and c) to grab the pre-built TCK bundle from
> Eclipse Download, {color}
> {color:#00}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the
> list of the {color}
> {color:#00}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with
> Tomcat.{color}
> {color:#00}{color:#00}The{color} [6] is the official list of the
> instructions.{color}
>
> {color:#00}[1]
> {color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[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)
[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:
--
Attachment: (was: JTwork- 26-December-2019.zip)
> 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:#00}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#00}grabbed pre-built), configured, and run [1].{color}
> * {color:#00}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#00}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#00}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#00}manage all that [2].{color}
> * {color:#00}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#00}the API artifact built by a Jenkins build job and integrate
> it to a {color}
> {color:#00}Glassfish and c) to grab the pre-built TCK bundle from
> Eclipse Download, {color}
> {color:#00}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the
> list of the {color}
> {color:#00}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with
> Tomcat.{color}
> {color:#00}{color:#00}The{color} [6] is the official list of the
> instructions.{color}
>
> {color:#00}[1]
> {color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[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)
[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:
--
Attachment: JTwork- 26-December-2019.zip
> 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, 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:#00}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#00}grabbed pre-built), configured, and run [1].{color}
> * {color:#00}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#00}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#00}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#00}manage all that [2].{color}
> * {color:#00}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#00}the API artifact built by a Jenkins build job and integrate
> it to a {color}
> {color:#00}Glassfish and c) to grab the pre-built TCK bundle from
> Eclipse Download, {color}
> {color:#00}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the
> list of the {color}
> {color:#00}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with
> Tomcat.{color}
> {color:#00}{color:#00}The{color} [6] is the official list of the
> instructions.{color}
>
> {color:#00}[1]
> {color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[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)
[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:
--
Attachment: JTwork- 26-December-2019.zip
JTreport-26-December-2019.zip
> 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, 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:#00}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#00}grabbed pre-built), configured, and run [1].{color}
> * {color:#00}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#00}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#00}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#00}manage all that [2].{color}
> * {color:#00}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#00}the API artifact built by a Jenkins build job and integrate
> it to a {color}
> {color:#00}Glassfish and c) to grab the pre-built TCK bundle from
> Eclipse Download, {color}
> {color:#00}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the
> list of the {color}
> {color:#00}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#00}finished [4].{color}
> {color:#00}The [5] is the example how to run Jakarta EE TCKs with
> Tomcat.{color}
> {color:#00}{color:#00}The{color} [6] is the official list of the
> instructions.{color}
>
> {color:#00}[1]
> {color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
>
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[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)
[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-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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
b) to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new
API {color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can
be {color}
{color:#00}finished [4].{color}
{color:#00}The [5] is the example how to run Jakarta EE TCKs with
Tomcat.{color}
{color:#00}{color:#00}The{color} [6] is the official list of the
instructions.{color}
{color:#00}[1]
{color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[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-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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file, b)
to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new API
{color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can be
{color}
{color:#00}finished [4].{color}
{color:#00}[1]
{color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[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-59bdc7a54...@apache.org%3E
> Jakarta EE TCK:
>
[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-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:#00}We have summed up some information about how the TCK can be
built (or {color}
{color:#00}grabbed pre-built), configured, and run [1].{color}
* {color:#00}This is assumed to be run against a Glassfish with the latest
API {color}
{color:#00}integrated (replacing the original API in the Glassfish).{color}
* {color:#00}We have created a recording of a presentation of the Jenkins
jobs that {color}
{color:#00}manage all that [2].{color}
* {color:#00}We have created 3 Jenkins files for pipeline job (as an
example for {color}
{color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file, b)
to grab {color}
{color:#00}the API artifact built by a Jenkins build job and integrate it
to a {color}
{color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
Download, {color}
{color:#00}grab the configured ts.jte file, grab the Glassfish with new API
{color}
{color:#00}integrated, and run the TCK [3].{color}
{color:#00}For the complete information, please allow me to mention the
list of the {color}
{color:#00}TCK tasks needed to be done before the Jakarta EE release can be
{color}
{color:#00}finished [4].{color}
{color:#00}[1]
{color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
{color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
{color:#00}[3] {color}
+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
{color:#00}[4] {color}+[https://github.com/orgs/eclipse-ee4j/projects/14]+
was:
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
> 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-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:#00}We have summed up some information about how the TCK can be
> built (or {color}
> {color:#00}grabbed pre-built), configured, and run [1].{color}
> * {color:#00}This is assumed to be run against a Glassfish with the
> latest API {color}
> {color:#00}integrated (replacing the original API in the
> Glassfish).{color}
> * {color:#00}We have created a recording of a presentation of the
> Jenkins jobs that {color}
> {color:#00}manage all that [2].{color}
> * {color:#00}We have created 3 Jenkins files for pipeline job (as an
> example for {color}
> {color:#00}JSON-B TCK) to a) properly set the ts.jte configuration file,
> b) to grab {color}
> {color:#00}the API artifact built by a Jenkins build job and integrate it
> to a {color}
> {color:#00}Glassfish and c) to grab the pre-built TCK bundle from Eclipse
> Download, {color}
> {color:#00}grab the configured ts.jte file, grab the Glassfish with new
> API {color}
> {color:#00}integrated, and run the TCK [3].{color}
> {color:#00}For the complete information, please allow me to mention the
> list of the {color}
> {color:#00}TCK tasks needed to be done before the Jakarta EE release can
> be {color}
> {color:#00}finished [4].{color}
> {color:#00}[1]
> {color}+[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run]+
> {color:#00}[2] {color}+[https://youtu.be/nnD1KMvh0to]+
> {color:#00}[3] {color}
> +[https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines]+
> {color:#00}[4] {color}+[https://github.com/orgs/eclipse-ee4j/projects/14]+
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[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-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 was: 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 > 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-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 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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-59bdc7a54...@apache.org%3E https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck > 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-59bdc7a54...@apache.org%3E > https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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-59bdc7a54...@apache.org%3E Jakarta EE TCK: https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck was: Mail thread: https://mail-archives.apache.org/mod_mbox/cxf-dev/201901.mbox/%3C6edd1da6-d651- e2a3-8092-59bdc7a54...@apache.org%3E https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck > 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-59bdc7a54...@apache.org%3E > Jakarta EE TCK: https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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-59bdc7a54...@apache.org%3E https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck was: Mail thread: https://mail-archives.apache.org/mod_mbox/cxf-dev/201901.mbox/%3c6edd1da6-d651-e2a3-8092-59bdc7a54...@apache.org%3E https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck > 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-59bdc7a54...@apache.org%3E > https://projects.eclipse.org/proposals/eclipse-jakarta-ee-tck -- This message was sent by Atlassian JIRA (v7.6.3#76005)
