Details
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8279925 | 17.0.3 | Andrew Leonard | P4 | Resolved | Fixed | b01 |
Description
Currently Jar and Jmod implementation will timestamp newly created entries with the Current Time or the source file last modified timestamp.
To enable "reproducible builds" the jar and jmod tooling need the ability to specify a "source-date" (akin to SOURCE_DATE_EPOCH standard), so that the generated content optionally has a specified "timestamp".
This enhancement proposes the following changes:
- jar and jmod:
- New option: --source-date <timestamp>
When set content entry timestamps will be set to the given <timestamp>
To enable "reproducible builds" the jar and jmod tooling need the ability to specify a "source-date" (akin to SOURCE_DATE_EPOCH standard), so that the generated content optionally has a specified "timestamp".
This enhancement proposes the following changes:
- jar and jmod:
- New option: --source-date <timestamp>
When set content entry timestamps will be set to the given <timestamp>
Attachments
Issue Links
- backported by
-
JDK-8279925 Enable jar and jmod to produce deterministic timestamped content
-
- Resolved
-
- csr for
-
JDK-8277755 Enable jar and jmod to produce deterministic timestamped content
-
- Closed
-
- relates to
-
JDK-8279453 Disable tools/jar/ReproducibleJar.java on 32-bit platforms
-
- Resolved
-
-
JDK-8276400 JDK tools should support SOURCE_DATE_EPOCH
-
- Closed
-
- links to
-
Commit openjdk/jdk17u-dev/761e2989
-
Commit openjdk/jdk/db68a0ce
-
Review openjdk/jdk17u-dev/82
-
Review openjdk/jdk/6481
(3 links to)