-
Bug
-
Resolution: Fixed
-
P1
-
1.4.2_01
-
01
-
x86
-
windows_xp
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2070987 | 5.0 | Kumar Srinivasan | P1 | Closed | Fixed | 5.0 |
JDK-2070986 | 1.4.2 | Kumar Srinivasan | P1 | Resolved | Fixed | b28 |
Because of fix in #4804185: Unpack does not produce crc/date/time attributes in jars, the date/time attributes in jar entries in the jar file after unpack are set to the time unpack is executed. However, this creates a big problem to Java Update because the resulting jar files after unpack will be different everytime the installer runs, thus making the base image completely unstable and patching will fail during Java Update.
Installing the 5.5.5_01 PIT build in Java Update testing, typing java -version will yield
java version "5.5.5-test"
Java(TM) 2 Runtime Environment, Standard Edition (build 5.5.5_01-test-b01)
Java HotSpot(TM) Client VM (build 5.5.5_01-test-b01, mixed mode)
Notice that the java version is "5.5.5-test" instead of "5.5.5_01-test". Patching on jar files fail in 5.5.5_01 because of the unpack changes. Thus, while the VM and java.exe are patched correctly from 5.5.5 to 5.5.5_01 versions, rt.jar and other jar files are left behind as the 5.5.5 version, thus resulting in the above behavior. Looking at the PATCH.ERR file in 5.5.5_01 also reveals this problem about patching failure.
###@###.### 2003-06-16
###@###.### 2003-06-16
Installing the 5.5.5_01 PIT build in Java Update testing, typing java -version will yield
java version "5.5.5-test"
Java(TM) 2 Runtime Environment, Standard Edition (build 5.5.5_01-test-b01)
Java HotSpot(TM) Client VM (build 5.5.5_01-test-b01, mixed mode)
Notice that the java version is "5.5.5-test" instead of "5.5.5_01-test". Patching on jar files fail in 5.5.5_01 because of the unpack changes. Thus, while the VM and java.exe are patched correctly from 5.5.5 to 5.5.5_01 versions, rt.jar and other jar files are left behind as the 5.5.5 version, thus resulting in the above behavior. Looking at the PATCH.ERR file in 5.5.5_01 also reveals this problem about patching failure.
###@###.### 2003-06-16
###@###.### 2003-06-16
- backported by
-
JDK-2070986 Random date/time attributes produced in jars through unpack breaks Java Update
-
- Resolved
-
-
JDK-2070987 Random date/time attributes produced in jars through unpack breaks Java Update
-
- Closed
-