-
Bug
-
Resolution: Fixed
-
P3
-
6u22
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2204286 | 6-pool | Abhijit Saha | P3 | Closed | Won't Fix | |
JDK-2202278 | 6u22-rev | Abhijit Saha | P3 | Closed | Fixed | b09 |
FULL PRODUCT VERSION :
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.1.7600]
A DESCRIPTION OF THE PROBLEM :
In JDK 6u22, pack200 --version does not print its version and modified date correctly as it did so in previous versions.
Of course, this issue itself does not hit me hard at all, but supposed changes in JDK integration process made my life a bit harder. I have been continuously monitoring JDK sources to see which change may or may not affect our products. However, since keywords are no longer expanded in the source code files bundled with JDK 6u22, almost all files contain non-relevant changes from previous versions. So I had to strip all comments before comparing the sources between 6u21 and 6u22. Please consider improve the JDK source release process so everyone around the world like me can do the task like the one mentioned above much more easily.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
An output similar to the one from the previous versions like this:
com.sun.java.util.jar.pack.Driver version 1.26, 10/03/23
ACTUAL -
com.sun.java.util.jar.pack.Driver version %I%, %E%
REPRODUCIBILITY :
This bug can be reproduced always.
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.1.7600]
A DESCRIPTION OF THE PROBLEM :
In JDK 6u22, pack200 --version does not print its version and modified date correctly as it did so in previous versions.
Of course, this issue itself does not hit me hard at all, but supposed changes in JDK integration process made my life a bit harder. I have been continuously monitoring JDK sources to see which change may or may not affect our products. However, since keywords are no longer expanded in the source code files bundled with JDK 6u22, almost all files contain non-relevant changes from previous versions. So I had to strip all comments before comparing the sources between 6u21 and 6u22. Please consider improve the JDK source release process so everyone around the world like me can do the task like the one mentioned above much more easily.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
An output similar to the one from the previous versions like this:
com.sun.java.util.jar.pack.Driver version 1.26, 10/03/23
ACTUAL -
com.sun.java.util.jar.pack.Driver version %I%, %E%
REPRODUCIBILITY :
This bug can be reproduced always.
- backported by
-
JDK-2202278 pack200 --version does not print its version correctly in 6u22
- Closed
-
JDK-2204286 pack200 --version does not print its version correctly in 6u22
- Closed