Is this all just historical crud that can be simplified now, or is there some deeper significance?
Does anyone know why jenkins-test-harness is configured so "specially"? It seems to run Surefire on one source file, which is in both src/test/junit4 and
target/generated-sources (??), and then run everything else though something called maven-junit-plugin... whose reason for existence seems to be to run tests in parallel,
even though Surefire can do that as well.
