[
https://issues.apache.org/jira/browse/MSHARED-1445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17889452#comment-17889452
]
Herve Boutemy commented on MSHARED-1445:
----------------------------------------
any reference why there is a min? Is 0 as Unix SOURCE_DATE_EPOCH value not
valid in Java?
(then we'll need to update some documentation on it to advise against using
single digit value)
side question: what is SOURCE_DATE_EPOCH value for 1980-01-01T00:00:02Z?
> Unix timestamps since the epoch are not subject to the boundary checks
> ----------------------------------------------------------------------
>
> Key: MSHARED-1445
> URL: https://issues.apache.org/jira/browse/MSHARED-1445
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: maven-archiver-3.6.2
> Reporter: Michael Osipov
> Assignee: Michael Osipov
> Priority: Critical
> Fix For: maven-archiver-4.0.0, maven-archiver-3.6.3,
> maven-archiver-4.0.0-beta-2
>
>
> The Javadoc says:
> {noformat}
> * @throws IllegalArgumentException if the outputTimestamp is neither ISO 8601
> nor an integer, or it's not within
> * the valid range 1980-01-01T00:00:02Z to 2099-12-31T23:59:59Z
> {noformat}
> but when a Unix timestamp since the epoch is passed it is simply passed
> through. No min/max check. We need to fix this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
