[jira] [Work logged] (CXF-8192) Upgrade jaxb runtime to 2.3.3-b02
[ https://issues.apache.org/jira/browse/CXF-8192?focusedWorklogId=372154=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-372154 ] ASF GitHub Bot logged work on CXF-8192: --- Author: ASF GitHub Bot Created on: 15/Jan/20 06:39 Start Date: 15/Jan/20 06:39 Worklog Time Spent: 10m Work Description: jimma commented on pull request #625: [CXF-8192]:Upgrade jaxb runtime to 2.3.3-b02 URL: https://github.com/apache/cxf/pull/625 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 372154) Remaining Estimate: 0h Time Spent: 10m > Upgrade jaxb runtime to 2.3.3-b02 > - > > Key: CXF-8192 > URL: https://issues.apache.org/jira/browse/CXF-8192 > Project: CXF > Issue Type: Task > Components: JAXB Databinding >Affects Versions: 3.3.4 >Reporter: Jim Ma >Assignee: Jim Ma >Priority: Major > Fix For: 3.4.0, 3.3.6 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CXF-8192) Upgrade jaxb runtime to 2.3.3-b02
Jim Ma created CXF-8192: --- Summary: Upgrade jaxb runtime to 2.3.3-b02 Key: CXF-8192 URL: https://issues.apache.org/jira/browse/CXF-8192 Project: CXF Issue Type: Task Components: JAXB Databinding Affects Versions: 3.3.4 Reporter: Jim Ma Assignee: Jim Ma Fix For: 3.4.0, 3.3.6 -- 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}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] [Resolved] (CXF-8184) cxf-codegen-plugin fails sporadically with FOUND_NO_FRONTEND: NPE in AbstractToolContainer
[
https://issues.apache.org/jira/browse/CXF-8184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved CXF-8184.
--
Resolution: Not A Problem
Please re-open if the problem resurfaces
> cxf-codegen-plugin fails sporadically with FOUND_NO_FRONTEND: NPE in
> AbstractToolContainer
> --
>
> Key: CXF-8184
> URL: https://issues.apache.org/jira/browse/CXF-8184
> Project: CXF
> Issue Type: Bug
> Components: Tooling
>Affects Versions: 3.0.16
> Environment: Apache Maven 3.6.2
> (40f52333136460af0dc0d7232c0dc0bcf0d9e117; 2019-08-27T17:06:16+02:00)
> Maven home: /opt/apache-maven-3.6.2
> Java version: 1.8.0_231, vendor: Oracle Corporation, runtime:
> /opt/jdk1.8.0_231-CCS/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-1062.9.1.el7.x86_64", arch: "amd64",
> family: "unix"
>Reporter: Falko Modler
>Priority: Major
>
> From time to time the plugin fails with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.cxf:cxf-codegen-plugin:3.0.16:wsdl2java (default) on project
> some-project: Execution default of goal
> org.apache.cxf:cxf-codegen-plugin:3.0.16:wsdl2java failed: FOUND_NO_FRONTEND
> -> [Help 1]
> {noformat}
> {noformat:title=Further up in the log}
> java.lang.NullPointerException
> at
> org.apache.cxf.tools.common.toolspec.AbstractToolContainer.getBus(AbstractToolContainer.java:196)
> at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:195)
> at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:164)
> at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:412)
> at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:105)
> at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
> at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86)
> at
> org.apache.cxf.maven_plugin.wsdl2java.WSDL2JavaMojo.generate(WSDL2JavaMojo.java:427)
> at
> org.apache.cxf.maven_plugin.AbstractCodegenMoho.execute(AbstractCodegenMoho.java:321)
> at
> org.apache.cxf.maven_plugin.wsdl2java.WSDL2JavaMojo.execute(WSDL2JavaMojo.java:524)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:190)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:186)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> Looking at the
> [code|https://github.com/apache/cxf/blob/cxf-3.0.16/tools/common/src/main/java/org/apache/cxf/tools/common/toolspec/AbstractToolContainer.java#L196],
> it seems that the {{OASISCatalogManager}} bus extension is null.
> Please note that we use the parallel Maven build feature (-T) and we don't
> use the fork mode (which slows everything down considerably).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
