JDK-6833472 : allow J4B builds to be considered GA
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2009-04-23
  • Updated: 2010-04-04
  • Resolved: 2010-03-18
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.
JDK 6
6-poolResolved
Related Reports
Duplicate :  
JDK-6715420 - j4b revisions are not recognized as "platform versions"
Description
in javawebstart, and now the new plugin, version strings are parsed to determine if a build is GA or pre-GA, and only GA builds are considered when matching platform version specifications.
The old versioning spec says any full version string containing a hyphen character is pre-GA, like 1.6.0_10=ea or 1.7.0-rc.
However with the creation of J4B, post GA builds now have "-rev" in the full version string (like 1.6.0_12-rev02).
We should change the logic in javaws (and the new plugin) to consider GA any full version with "-rev" in the version string.
Comments
EVALUATION 6u18 includes fix to: 6715420: j4b revisions are not recognized as "platform versions" which is the same thing as this - closing as a dupe
18-03-2010
EVALUATION see proposed fix in comments
23-04-2009