You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ismaël Mejía (JIRA)" <ji...@apache.org> on 2019/04/26 20:05:00 UTC
[jira] [Assigned] (BEAM-2727) Make Beam released artifacts
reproducible
[ https://issues.apache.org/jira/browse/BEAM-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ismaël Mejía reassigned BEAM-2727:
----------------------------------
Assignee: (was: Ismaël Mejía)
> Make Beam released artifacts reproducible
> -----------------------------------------
>
> Key: BEAM-2727
> URL: https://issues.apache.org/jira/browse/BEAM-2727
> Project: Beam
> Issue Type: Improvement
> Components: build-system
> Affects Versions: Not applicable
> Reporter: Ismaël Mejía
> Priority: Minor
> Labels: triaged
>
> There is a recent movement to create a verifiable path from source code to binary releases in different open source projects. See http://reproducible-builds.org/
> For the case of Java binaries (classes and jars) if we want to have a reproducible build we need to have a consistent build environment so we can reproduce those.
> For Beam we need to create an environment with a fixed version of the Java compiler, maven and its plugins. This is addressed by BEAM-1534. But also by including the (JDK/Maven versions) used to generate the jar artifacts in the information to validate at the vote. Additionally we need to fix the Jar files because by default the maven-jar-plugin include the timestamp of the build in the files which breaks the reproducibility of the process, fortunately there is a Maven plugin that fixes this and that we can include in the release build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)