Hi,
I've noticed some unsatisfying discussions regarding surefire, so let me
try to help moving this forward.
Here's the situation as I see it:
- Surefire 2.20.1 is the latest released version (2017-09-15)
- 2.20.1 doesn't use the modulepath yet, that will be part of the next
release. A lot of people are waiting for this even before the official
release of JDK9.
- Surefire 2.x is is still JDK 1.6 compatible, the requirement of JDK 1.7
is planned for surefire 3.0.0
- 2.20.1 doesn't run on JDK10, it gets an NPE caused by commons-lang when
trying to get the Java version. The version of commons-lang where this is
fixed required JDK 1.7 (which clashes with the previous bullet)
- After the next version (2.21), surefire will focus on 3.0.0
- There's no agreement that the current master works with JDK10. One of
the things I noticed is that you need to run surefire with a special set
of arguments. I haven't been able to build it locally, so I cannot judge
it.
- Surefire is a huge, complex project and Tibor has taken the
responsibility for maintaining this project.
What I would like to see is:
- What's blocking a release right now? Is it just CI? Knowing that CI has
changed a lot the last couple of months, did it just expose *unknown
issues* compared to 2.20.1?
- Is the master at its current state already an improvement compared to
2.20.1?
- What would be the estimated release date for surefire.
- If this date is too unsure or takes too long, can Olivier create a
branch and do a 21.1-JDK10 release? or beta1?
My main issue is : we should work towards a new release, because 2.20.1
doesn't work with JDK10 and there's no workaround.
IMHO this doesn't have to be an official surefire release, we can add some
special qualifier to at least help those who need to work with JDK10.
thanks,
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
