Issue/27

[MarkusTiede]

Fixes #27

[bsolar17]

Rationale to set useSystemClassLoader to false is not clear: I understand it fixes the ForkedBooter class loading failure, but why? I tried to follow the linked CircleCI thread but didn't find this information quickly enough.

[MarkusTiede]

I'm not sure whether digging into the why of classloading in maven / surefire is really necessary.

This PR already shows that it's effective:

As far as I understand it's valid (widely) used workaround for this issue. What's a / the solution you'd prefere @bsolar17 ? In my opinion the other thing would be

1. no longer build (until resolved) on circle CI
2. disable surefire test execution in that environment
3. downgrade the openjdk base container used for building at circle CI

Some details are also available on a corresponding debian bug report.

[bsolar17]

Ok, reading the Debian issue, if I understand correctly their Java8 package has a bug which makes JAR checking fail and they have backported a fix from Java11 to correct it. This backport is relatively recent and I guess the new version of the Java8 package is not being used yet in CircleCI, leading to the need for a workaround which is the useSystemClassLoader=false setting.

This is the kind of information I'd like to have together with a change: not only whether it's effective but also why it's needed in the first place (and why it might not be needed anymore in the future, e.g. when the fixed Java8 package is deployed).