-
Bug
-
Resolution: Fixed
-
P3
-
None
-
b68
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8004869 | 7u21 | Andy Herrick | P3 | Closed | Fixed | b05 |
generally we write the deployment.properties file from javaws native launcher if :
1.) The registered set of JREs have changed.
2.) the args: "-userConfig <property> <name>" are used.
For 1.) we need to do the same computation of the available set of JREs that we do now, just not write it to the deployment.properties file. (we will need to insure that at the java level, if the set of jres is updated, we update the deployment.properties file.)
For 2.) we need to invoke the JCP with it's new args (added for 7u10) to set the property correctly.
1.) The registered set of JREs have changed.
2.) the args: "-userConfig <property> <name>" are used.
For 1.) we need to do the same computation of the available set of JREs that we do now, just not write it to the deployment.properties file. (we will need to insure that at the java level, if the set of jres is updated, we update the deployment.properties file.)
For 2.) we need to invoke the JCP with it's new args (added for 7u10) to set the property correctly.
- backported by
-
JDK-8004869 Remove code from native javaws launcher to write the users deployment.properties file.
-
- Closed
-