JDK-8075526 : Need a way to read and write ZipEntry timestamp using local date/time without tz conversion
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.util.jar
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2015-03-19
  • Updated: 2018-12-20
  • Resolved: 2015-07-22
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b75Fixed
Related Reports
Blocks :  
JDK-8073187 - Unexpected side effect in Pack200
Relates :  
JDK-8161942 - java.util.zip.ZipEntry.java not covering UpperLimit range of DOS epoch
Description
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 in JDK-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).