JDK-6895287 : disable building fontchecker
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 7
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2009-10-26
  • Updated: 2010-04-04
  • Resolved: 2009-11-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7 b76Fixed
Related Reports
Relates :  
JDK-6795908 - Refactor FontManager
Description
With the change to FontManager (see 6795908), getFontPath(boolean) is now in
SunFontManager on JDK7 making it impossible to bootstrap with OpenJDK7
itself (SunFontManager.getFontPath(boolean))  and OpenJDK6
(FontManager.getFontPath(boolean)).
Comments
SUGGESTED FIX http://hg.openjdk.java.net/jdk7/build/jdk/rev/9bc5338675e0 Fix contributed by Andrew John Hughes.
29-10-2009
EVALUATION We could stop building fontchecker and discard it. It was introduced in the 1.4.2 when we had native code that sometimes crashed the JRE on seeing a bad font file. The windows jre installer used it in 1.4.2 and 1.5. The installer stopped using it in 1.6 (6239557) but we continued to build it. There's also a version in the closed/src/test directory that was intended as a standalone manual test tool, but can't have been buildable since 1.4.x days! This can be removed.
26-10-2009