[
https://issues.apache.org/jira/browse/CAMEL-12586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515045#comment-16515045
]
Zoran Regvart commented on CAMEL-12586:
---------------------------------------
Oh not an issue [~pascalschumacher] I think I even created the issue after you
did the upgrade. I found a series of issues with Surefire from 2.19 onwards,
and probably the cause for using 2.18.1 or 2.16 (SUREFIRE-1302, SUREFIRE-1374).
And I've experimented with {{camel-example-cdi-xml}} and upgrading to 2.22
works but it's flaky in very low percentages, I had to run {{mvn test}} for a
while to find any issue. Let me experiment just a bit more to see if I can make
all versions of Surefire be 2.22.
> Use consistant Surefire and JAXB version
> ----------------------------------------
>
> Key: CAMEL-12586
> URL: https://issues.apache.org/jira/browse/CAMEL-12586
> Project: Camel
> Issue Type: Task
> Components: build system
> Reporter: Zoran Regvart
> Assignee: Zoran Regvart
> Priority: Major
> Fix For: 2.22.0
>
>
> Seems that our daily build fails as the {{maven-surefire-plugin}} configured
> in JDK 9+ profile requires a version of {{jaxb-core}} that's no(t) (longer)
> available on Maven Central. And with SUREFIRE-1330 in 2.22.0 it opens the use
> of JUnit5 in Camel.
> Might be worth taking a look and use the same {{maven-surefire-plugin}}
> versions across all modules, some seem to be using version 2.19.1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
