[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jakartaee-tck-dev] [External] : Jenkins failure caused by "javax.xml.bind.JAXBException: Implementation of JAXB-API has not been found on module path or classpath"???
|
I created
https://github.com/eclipse-ee4j/jakartaee-tck/issues/614 as a
reminder of the settings that used to work for when we enable
"Publish Junit reports generated with handlebars" again in the
future.
Scott
On 2/8/21 10:55 AM, Scott Marlow wrote:
On 2/6/21 3:56 AM, Alwin Joseph
wrote:
Hi
Scott,
This
is due to the junit report generation plugin which got
upgraded recently and does not relate to the actual tck
runs.. I had filed an issue [1] for this in eclipse infra.
From the bug : “plugin .. is not compatible with
JDK11 and needs to be adapted.
If you can't live without this plugin, I'd
recommend to open an issue in it's GitHub issue tracker.
Otherwise, do not use it.
“
As a temporary solution I removed the task from the
post-build step. The plugin was quite useful to view the
test report, I think we can open an issue in the github
issue tracker and wait.
+1, I opened
https://github.com/web-innovate/bootstraped-multi-test-results-report/issues/92
requesting JDK 11 support.
I will remove the "Publish Junit reports generated with
handlebars" plugin from the 9.0.x Jenkins jobs as well.
Scott
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
