JDK-6748350 : REGRESSION:Eclipse does not pick up the correct theme for Vista
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6u10
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_vista
  • CPU: x86
  • Submitted: 2008-09-15
  • Updated: 2011-01-19
  • Resolved: 2008-09-24
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.
6u10 b33Fixed
Related Reports
Duplicate :  
Relates :  
Relates :  
J2SE Version (please include all output from java -version flag):
  java version "1.6.0_10-rc2"
  Java(TM) SE Runtime Environment (build 1.6.0_10-rc2-b31)
  Java HotSpot(TM) Client VM (build 11.0-b15, mixed mode, sharing)

Does this problem occur on J2SE 1.3, 1.4.x or 1.5?  Yes / No (pick one)

Operating System Configuration Information (be specific):
  Windows Vista SP1 [6.0.6001], Brazilian Portuguese, fully patched

Hardware Configuration Information (be specific):
  Dell Precision T3400 (Intel Core2 Quad Q6600; NVidia Quadro FX1700)

Bug Description:
When I run the Eclipse IDE (version 3.4.0), it doesn't pick up the correct theme for Vista. Notice that this problem is specific to SWT (Standard Widget Toolkit), the GUI toolkit from the Eclipse Foundation. But it's probably a regression from some change in AWT or Java2D, as SWT relies partially on these JavaSE APIs for some low-level and configuration stuff. And the bug is specific to b31, it doesn't happen in any previous build of 6u10, grom the first public builds to b28 (I use Eclipse almost daily, and I always run the latest 6u10 build, so I tested them all).

Steps to Reproduce (be specific):
Just run the Eclipse IDE and check the views tht use tree, list and progress controls; they are all wrong. I posted this issue at the Eclipse bugtrack system, check here for details, evidence, and discussion with the Eclipse developers:

I consider this bug very important, even though SWT is not a standard JavaSE or JCP API. The Eclipse platform is very popular and this bug is a blocker for adoption of Java SE 6 Update 10 for Eclipse users (and also, users of any app build with SWT or Eclipse RCP) in the Vista platform.

EVALUATION Having two manifest files follows to the Microsoft OEM cerification tests failure, sigcheck tool dumps only one the manifests. Therefore, it seems like the only way to fix the L&F problems (without breaking the fix for the OEM tests) is to merge these manifests. The template.manifest file covers all JRE .exe files, so the fix affects all launchers.

SUGGESTED FIX new version of the fix is here http://sa.sfbay.sun.com/projects/awt_data/6u10/6748350.1

EVALUATION This is a regression of the fix for 6722527, the fix adds the manifest for the execution level and it also removes the AWT-specific manifest, java.exe needs the AWT-specific manifest which include dependency to the common control library.

SUGGESTED FIX http://sa.sfbay.sun.com/projects/awt_data/6u10/6748350.0/

EVALUATION This problem is observed for several components in JDK, at least for AWT file/pring dialogs and (which is much more important) for JavaKernel dialogs. As 6u10 is a base release for JavaFX, it is unacceptable to have such ugly Win2K-styled components in our dialogs.