If they specify something on the command line, and that doesn't exist,
then we end up with Pisces even if Ductus is available. Is that
intentional?
Also, why the switch from "getProperty(, default)" to the basic
getProperty() and manually applying the default?
...jim
On 5/7/14 11:26 AM, Phil Race wrote:
https://bugs.openjdk.java.net/browse/JDK-8038875
http://cr.openjdk.java.net/~prr/8038875/
This is in support of modularisation (ie jigsaw). After the fix
alternate implementations
are loaded using Class.forName() as specified by the system property
sun.java2d.renderer. Note that only the built-in ones are actually
supported
The mechanism is just for testing.
BTW since it happens that Oracle JDK includes the pisces classes as well
as the closed source ductus I note that its possible to compare the
performance
or other characteristics easily in a closed build which has both by
specifying
to use pisces instead of ductus.
There's no regression test associated with this. I tested open & closed
builds
(created for all platforms) with standard demos.
-phil.
