Plugin automatically adds entries of the form "deployment.javapi.jre.<JRE_VERSION>.*" to the Deploy properties file for the current JRE if they are not already present. There is a discrepancy between the version string used on Unix and Windows.
For example, given any non-FCS release, such as 1.6.0 Early Access, the value of System.getProperty("java.version") is "1.6.0-ea". This is the same string used in "deployment.javapi.jre.<JRE_VERSION>.*" properties on Unix. Whereas Windows uses only "1.6.0".
The two platforms should be consistent. Since the full string, including the release tag, was used on all systems prior to 1.5.0, this should be the string used. (Note: Java Web Start has a similar set of properties, and it uses the value from "java.version" on all platforms.)
This bug can be recreated on Windows by deleting the Deployment properties file, and then running Plugin. Plugin will automatically create the properties, and they will have the incorrect values.
###@###.### 2005-05-10 19:23:09 GMT
For example, given any non-FCS release, such as 1.6.0 Early Access, the value of System.getProperty("java.version") is "1.6.0-ea". This is the same string used in "deployment.javapi.jre.<JRE_VERSION>.*" properties on Unix. Whereas Windows uses only "1.6.0".
The two platforms should be consistent. Since the full string, including the release tag, was used on all systems prior to 1.5.0, this should be the string used. (Note: Java Web Start has a similar set of properties, and it uses the value from "java.version" on all platforms.)
This bug can be recreated on Windows by deleting the Deployment properties file, and then running Plugin. Plugin will automatically create the properties, and they will have the incorrect values.
###@###.### 2005-05-10 19:23:09 GMT
- relates to
-
JDK-6308262 java.home, java.runtime.version pointing to old jre values even after browser jre is changed
-
- Closed
-