[
https://issues.apache.org/jira/browse/MSHARED-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914576#comment-17914576
]
Delany commented on MSHARED-1460:
---------------------------------
[~elh...@metalab.unc.edu] i'll sort out the tests, but is this an acceptable
change? It seems that the constraint on the build output timestamp has been
added for the purposes of reproducible builds (and nothing else). If the
thinking is that no JARs were made before 1980 anyway, then why should it
matter that I have a JAR which says it was? I don't even know which JAR is
causing the issue, but I'm just the consumer and Maven should allow me to use
it.
> Default to minimum date when parsing build output timestamp
> -----------------------------------------------------------
>
> Key: MSHARED-1460
> URL: https://issues.apache.org/jira/browse/MSHARED-1460
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-archiver
> Affects Versions: maven-archiver-3.6.3
> Reporter: Delany
> Priority: Major
>
> MavenArchiver.parseBuildOutputTimestamp throws an IllegalArgumentException
> when it could just return the DATE_MIN and potentially log a warning.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
