JDK-6672972 : The "JRE Finder" wizard in JCP's Java Runtime Settings dialog doesn't see j2re-image as valid jre
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2008-03-08
  • Updated: 2010-09-08
  • Resolved: 2008-04-03
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 b21Fixed
This is with 6u10b13 (probably reproducible with earlier builds as well).

I point the Java Control Panel's "JRE Finder" wizard to a j2re-image
directory (a result of 'make image-jre' in j2se ws), but it doesn't
recognize it as proper jre.

SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u10/6672972.1

EVALUATION When the "JRE finder" wizard was generalized to work with the new Java Plug-In, the way it identified a JRE was looking for lib/deploy.jar. This mechanism doesn't work well for most JRE developers who don't build the deploy workspace but who may want to run their development builds with the new Java Plug-In. A better detection mechanism is to look for bin/java{.exe}, while ensuring that jre/bin/java{.exe} does not exist. This prevents accidentally running on top of a JDK's java executable, which is not supported.

EVALUATION The JRE finder for the Java Plug-In is looking for lib/deploy.jar. We should probably look for bin/java[.exe] or similar so that JDK developers can use their built images with the new plug-in instead of requiring them to build the deploy workspace as well.

WORK AROUND copy deploy.jar from any j2re image to j2re-image/lib