JDK-5008556 : Cannot set different runtime parameters for different 1.4.2_x versions
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.4.2
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2004-03-05
  • Updated: 2004-07-22
  • Resolved: 2004-06-25
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.
Other
1.4.2_06 06Fixed
Description
With the change in the deployment structure for the 1.4.2 plugin, there is no longer any way to specify different runtime parameters for different JRE versions.  For example, if you have both 1.4.2 and 1.4.2_03 installed on a Windows system, and you change the Java runtime parameters for 1.4.2 using C:\Program Files\Java\j2re1.4.2\bin\jpicpl32.exe, this will also change the runtime parameters for 1.4.2_03.

Version-specific properties are no longer written to individual properties files like they were prior to 1.4.2 (i.e. C;\Documents and Settings\Administrator\.java\properties141).  Instead, they are being written to the C:\Documents and Settings\Administrator\Application Data\Sun\Java\Deployment\deployment.properties files.  While the deployment.properties file contains version-specific information for 1.5.0+ (i.e. deployment.javapi.jre.1.5.0.args=-verbose), it only contains one generic entry for all 1.4.2 versions (i.e. deployment.javapi.jre.args=-verbose).


Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_06 generic FIXED IN: 1.4.2_06 INTEGRATED IN: 1.4.2_06 VERIFIED IN: 1.4.2_06
2004-07-23

EVALUATION In 1.4.2_0x we cannot simply add a new propert like javaplugin.jre.VERSION.params because this would mean that the plugin launcher would have to know about this property and use it. This could be possible going forward but then previous 1.4.2_0x versions that do not know about this property would not use it and use javaplugin.jre.params. This is why I propose that we still use javaplugin.jre.params for the params to be used with the currently selected jre, but also maintain javaplugin.jre.VERSION.params for each version that has parameters set. This way if parameters have been set for a particular jre they will stored in the deployment.properties file and can be used by setting javaplugin.jre.params equal to them when the respective jre is selected. ###@###.### 2004-04-01
2004-04-01