[
https://issues.apache.org/jira/browse/MSHARED-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16196032#comment-16196032
]
Zlika commented on MSHARED-661:
-------------------------------
That's true on a theoretical point of view. However in pratice you will have
exactly the same build result with Maven 3.0 and Maven 3.5, and with jdk8u0 and
jdk8u999. Adding this info just make the build more difficult to reproduce
because you need to use exactly the same Maven and jdk versions, and this info
is not easily available (you have to unpack the jar and look at the manifest,
unless you use maven-enforcer-plugin to explicitly enforce the Maven and jdk
versions). That's why I propose to have an option to disable all these
automatically added manifest entries.
> Make "Built-By", "Built-Jdk" and "Created-By" Manifest entries optional for
> reproducible builds
> -----------------------------------------------------------------------------------------------
>
> Key: MSHARED-661
> URL: https://issues.apache.org/jira/browse/MSHARED-661
> Project: Maven Shared Components
> Issue Type: New Feature
> Components: maven-archiver
> Reporter: Zlika
> Priority: Minor
>
> Maven-archiver automatically creates "Built-By", "Build-Jdk" and "Created-By"
> Manifest entries. In the frame of a reproducible build (cf. MNG-6276) these
> entries make the build not reproducible.
> Maven-archiver should propose an option to disable the creation of these
> non-reproducible manifest entries.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
