Hi all,
I'm going to close ISPN-2146 [1], which is
maven-surefire-plugin related
(SUREFIRE-879). The issue was temporarily solved on master by
switching
to maven-surefire-plugin 2.13-SNAPSHOT but it seems there
won't be any
stable 2.13 release soon so I'm going to switch to 2.12.2,
which now
also contains the SUREFIRE-879 fix.
I don't think I really care if we use 2.12.2 instead of
2.13, as long as your fix is in it. :)
I noticed some sub-modules use an older surefire version than
the parent
pom and I would like to upgrade those too unless there's a
voodoo reason
to use the old version. As an example, parent/pom.xml uses
maven-surefire-plugin version 2.4.3-JBOSS in traceTests
profile and
there's a comment that seems to indicate this version is
needed "to
avoid external log4j settings not being discovered when passed
as
command line arguments". I could not reproduce such an issue
with 2.12.2.
Yes, I'm pretty sure this is fixed in newer versions of
surefire.
Does anyone remember what issue is maven-surefire 2.4.3-JBOSS
solving?
Old versions of surefire didn't play nice with the parallel
test runner in core. It caused report files to overwrite one
another. If you can have a clean run with 2.12.x on Jenkins
and the reports look okay, then I'm happy to switch to 2.12.x
for all modules.
- M
--