-
Enhancement
-
Resolution: Fixed
-
P3
-
9
-
b75
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8136002 | emb-9 | Xueming Shen | P3 | Resolved | Fixed | team |
As of this writing the ZipEntry.setTime and getTime convert the timestamp (unix time long)
to default Timezone, this is a problem for pack200 and unpack200 implementations,
where the timestamps are stored in UTC, and in order to circumvent the current limitations
of getTime and setTime causes issues as described inJDK-8073187.
This is a request to add new APIs setTimeUTC and getTimeUTC which will write the
long as-is with no conversions, similar to POSIX gmtime(3C).
to default Timezone, this is a problem for pack200 and unpack200 implementations,
where the timestamps are stored in UTC, and in order to circumvent the current limitations
of getTime and setTime causes issues as described in
This is a request to add new APIs setTimeUTC and getTimeUTC which will write the
long as-is with no conversions, similar to POSIX gmtime(3C).
- backported by
-
JDK-8136002 Need a way to read and write ZipEntry timestamp using local date/time without tz conversion
- Resolved
- blocks
-
JDK-8073187 Unexpected side effect in Pack200
- Closed
- relates to
-
JDK-8161942 java.util.zip.ZipEntry.java not covering UpperLimit range of DOS epoch
- Closed