-
Bug
-
Resolution: Fixed
-
P2
-
1.4.0
-
beta3
-
sparc
-
solaris_2.6
-
Verified
In the Java Plug-in support for deploying Java optional packages (i.e. Java
3D), it uses the Java versioning string id naming convention in version checks. The version information, in the manifest of the jar file, must follow this format in order for the proper action to be taken (ex: upgrade). This information is missing from the Plug-in's "Deploying Java Optional Packages In Java Plug-in" document. The Java versioning string id naming convention needs to be added to this document. Have a link point to this document. If users do not know the format they may get unexpected results. There have been ?'s and bugs (4457286, 4466415) entered on this problem.
A copy of the Java versioning string id naming convention document can be
found at http://javaweb.eng/release/versioning.html
Product Version
Format is designated as "n.n" with maintenance releases being "n.n.n" and update releases being "n.n.n_nn" where "n" represents a numeric digit.
Vendor specific.
3D), it uses the Java versioning string id naming convention in version checks. The version information, in the manifest of the jar file, must follow this format in order for the proper action to be taken (ex: upgrade). This information is missing from the Plug-in's "Deploying Java Optional Packages In Java Plug-in" document. The Java versioning string id naming convention needs to be added to this document. Have a link point to this document. If users do not know the format they may get unexpected results. There have been ?'s and bugs (4457286, 4466415) entered on this problem.
A copy of the Java versioning string id naming convention document can be
found at http://javaweb.eng/release/versioning.html
Product Version
Format is designated as "n.n" with maintenance releases being "n.n.n" and update releases being "n.n.n_nn" where "n" represents a numeric digit.
Vendor specific.