[
https://issues.apache.org/jira/browse/MNG-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029160#comment-17029160
]
Herve Boutemy commented on MNG-6789:
------------------------------------
at least, it does not break reproducibility: I'm not against from this point of
view
is it worth to do it? I really don't know.
Thinking at it, I prefer to not have a "timestamp" property in build.properties
that does not really represent the timestamp of the build: now that we have
reproducible build, the timestamp of the build is something a notion that does
not have any interest since we get the same result whenever the effective build
is done
> Make Maven distribution build Reproducible
> ------------------------------------------
>
> Key: MNG-6789
> URL: https://issues.apache.org/jira/browse/MNG-6789
> Project: Maven
> Issue Type: Task
> Components: Bootstrap & Build
> Affects Versions: 3.6.2
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Priority: Major
> Fix For: 3.6.3
>
>
> with [Maven native Reproducible
> Builds|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=74682318]
> near available, it would be great to have Maven itself being the first Maven
> project that gets Reproducible Builds
> there is already a proof of concept available in reproducible branch:
> https://github.com/apache/maven/tree/reproducible with corresponding Jenkins
> build
> https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven/job/reproducible/
> once maven-jar-plugin, maven-assembly-plugin and maven-source-plugin have a
> reproducible release available, the last 2 plugins that bring non
> reproducible result in this build are plexus-component-metadata 2.0.0 and
> sisu-maven-plugin
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
