[MSHARED-1445] Unix timestamps since the epoch are not subject to the boundary checks

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: maven-archiver-3.6.2
• Fix Version/s: maven-archiver-4.0.0, maven-archiver-3.6.3, maven-archiver-4.0.0-beta-2
• Component/s: maven-archiver
• Assignee: Michael Osipov
• Reporter: Michael Osipov
• Created: 14/Oct/24 20:43
• Updated: 18/Oct/24 12:24
• Resolved: 18/Oct/24 12:23

Description

The Javadoc says:

* @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

but when a Unix timestamp since the epoch is passed it is simply passed through. No min/max check. We need to fix this.

Issue Links

• causes: MSHARED-1446 Add docs about repro build output timestamp boundaries
• Discovered while testing: MSITE-1018 LastPublicationTimestamp shows a fixed timestamp instead of the last build date
• is caused by: MSHARED-1067 Improve Reproducible Builds methods