Separating whitebox-api from jcstress-core - issues with 3rd-party libraries

[Aleksey Shipilev]

Hi Jerzy,

Your patch was attached with the incorrect MIME type:
 Content-Type: application/octet-stream; name="whitebox_api_separated.patch"

...and so was rejected by this mailing list.

On 02/22/2017 10:23 PM, Jerzy Krolak wrote:
> I've separated these on my PC and could successfully load a simple 
> Spring-based application. A jar with a single WhiteBox went to the
> bootclasspath, and jcstress-core stayed in the cp.

This raises deployment questions. We are targeting to always have a single JAR,
and putting whitebox.jar outside is an impediment for usability. I think putting
the compiled whitebox.jar into resources, dropping it to tempdir during the run,
and bootclasspath-ing it to forked JVM is a way to go.

> There are two potential issues with my patch:
> - a forked run loads the whitebox jar twice (one in boot cp and the other
> in regular one) - can it cause side effects?

Not pretty, but should not cause problems.

> - an unforked run won't load whitebox into bootcp at all (but I think it's
> the same behaviour as before) - same question here.

That's fine. There are many things that do not work with non-forked runs.
Non-forked mode was never meant to be reliable.

Thanks,
-Aleksey