-
Bug
-
Resolution: Fixed
-
P2
-
5.0u6
-
b01
-
generic
-
generic
when we do javaws import with alternatce codebase, the jnlp file timestamp we use is in the cache is incorrect. we just store with the current system time during the import happens, but we should have used the last-modified date from the alternate codebase.
jar resources are okay, problem is only with jnlp file.
this exists in tiger only, mustang is okay.
jar resources are okay, problem is only with jnlp file.
this exists in tiger only, mustang is okay.