On Dec 12, 2011, at 2:05 AM, Sean Owen wrote: > > It *seems* so much more like a test issue to me, solvable in the test > harness, and in a clear way: just split tests n ways across n JVMs instead > of 1 JVM with n threads. No (further) reliance on code being exactly well > behaved. It's just we don't have a one-liner to do that. Compared with > seasoning the code with ThreadLocal, and its associated small overhead, and > all the work to do that surgery, just feels very much like the hard way to > solve this.
Perhaps this will work, but the hard part is Maven doesn't offer batch granularity. It's either once or always for forking. Using always + parallel seems to yield no benefit in terms of performance.
