issues in converting from JDK6 to JDK7
Alan Snyder
javalists at cbfiddle.com
Tue Dec 10 09:42:53 PST 2013
I've waited until now to try to convert my applications to JDK7, and I am pleased at how well things are working.
I encountered two incompatibilities, however:
(1) I found that text rendered via Quaqua looked good (and normal) but text in the same font rendered by my code looked bad. Apparently the default setting for text antialiasing has changed. What is the thinking behind this change? What is the best way for me to accommodate this change? It looks like Quaqua alters the graphics context on every call to drawString. Is this what I should do?
(2) In a JDK6 application, the default values of java.ext.dirs and java.library.path both contain /Library/Java/Extensions and ~/Library/Java/Extensions. That is no longer true for java.library.path, which leads to failures to load Java libraries that contain native code. I can work around by adding /Library/Java/Extensions in a build script, but that approach does not work for ~/Library/Java/Extensions. I guess this is an appbundler issue? Is it an intentional change or a bug?
More information about the macosx-port-dev
mailing list