This can happen when the download fails, but there exists enough data to be unpacked before the unpacking fails (seee ).
As the partially unpacked files arent wiped, they will be started on the following maven run (probably detects as a successful installation). But they can't and cause the segfault (or even worse, don't cause a segfault and make your tests fail).
adding checksum support is the correct approach, but implementing it manually is the wrong approach.
instead, our plan ist which hopefully will fix this problem.
solved by switching to maven download mechanisms -