gnodet opened a new issue, #595: URL: https://github.com/apache/maven-jar-plugin/issues/595
## Problem\n\n 3.4.2 (via ) enforces a valid timestamp range of to on . When (Unix epoch, 1970) is set — a common reproducible-build convention used by Debian and many Apache projects — the build fails with:\n\n\n\nThis was working fine with 3.3.1. The range constraint comes from the ZIP/JAR format requiring timestamps ≥ 1980, which is correct for the JAR's internal entry timestamps — but the user-visible error message is confusing and there is no automatic clamping to .\n\n## Steps to reproduce\n\n1. Set (or ) in your build environment.\n2. Build a project using 3.4.2.\n3. Build fails with the above error.\n\n## Expected behavior\n\nEither:\n- **Clamp automatically**: If is before (1980-01-01T00:00:02Z), use instead and emit a warning. This is what many other tools do.\n- **Or reject with a clear message**: Document the minimum accepted value and link to the reproducible-builds guidance that must be ≥ (1980-01-01T00:00:02Z) when used with JDK jar tooling.\n\n ## Affected versions\n\n- 3.4.2 (regression vs 3.3.1)\n\n## Context\n\nFound while running Maven 4 compatibility tests across Apache projects. Affected projects: , .\n\nThe [Reproducible Builds mailing list](https://lists.reproducible-builds.org/pipermail/rb-general/2026-February/004045.html) documents that is commonly used and that the JDK tool imposes the 1980 floor — a clear error message or automatic clamping would help users.\n -- 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]
