[
https://issues.apache.org/jira/browse/MSHARED-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MSHARED-1446:
-------------------------------------
Fix Version/s: maven-archiver-4.0.0-beta-3
> Add docs about repro build output timestamp boundaries
> ------------------------------------------------------
>
> Key: MSHARED-1446
> URL: https://issues.apache.org/jira/browse/MSHARED-1446
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-archiver
> Affects Versions: maven-archiver-3.6.2
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Major
> Fix For: maven-archiver-4.0.0, maven-archiver-3.6.3,
> maven-archiver-4.0.0-beta-2, maven-archiver-4.0.0-beta-3
>
>
> In MSHARED-1067 the boundaries have been introduced, but never documented by
> they actually exist. Reason: MS-DOS time limitation for 2+2 bytes starting
> from 1980. See ZIP note:
> {quote}
> 4.4.6 date and time fields: (2 bytes each)
> The date and time are encoded in standard MS-DOS format.
> If input came from standard input, the date and time are
> those at which compression was started for this data.
> If encrypting the central directory and general purpose bit
> flag 13 is set indicating masking, the value stored in the
> Local Header will be zero. MS-DOS time format is different
> from more commonly used computer time formats such as
> UTC. For example, MS-DOS uses year values relative to 1980
> and 2 second precision.
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
