jira-importer commented on issue #190: URL: https://github.com/apache/maven-source-plugin/issues/190#issuecomment-2959554330
**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented thank you for the hint: I added some details to the output to confirm/show: on my machine, with Paris timezone UTC+2: ``` reproducible-1.0-sources.jar sha1 = 7bd062f9b45afb7423f3c004c8080ebad4e98754 encoding: UTF8 timezone offset (minutes): -120 M size (cmp) crc java time date time zip time mode name -comment; extra 8 25 ( 27) ee027fb2 1566419332000 2019-08-21 22:28:52 1326822298 100644 META-INF/MANIFEST.MF ; 0 ``` on ASF CI server, with UTC configuration: ``` reproducible-1.0-sources.jar sha1 = acf461ff37ddc3c44c620770a73d9cf42f7ca429 encoding: UTF8 timezone offset (minutes): 0 M size (cmp) crc java time date time zip time mode name -comment; extra 8 25 ( 27) ee027fb2 1566419332000 2019-08-21 20:28:52 1326818202 100644 META-INF/MANIFEST.MF ; 0 ``` as you can see from the "zip time field", which is the long value that is really stored in the zip stream, we get 1326822298 for a machine in UTC+2 but 1326818202 for a machine in UTC now, I'll update the code to trick the Java timestamp using local timezone: this will give unexpected different Dates in Java (should I say incorrect?), but from a zip stream perspective, we'll get the same value on every timezone Zip dates are tricky :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
