New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make build reproducible #96
Conversation
140fa5a
to
8f6a605
Compare
Hi @hboutemy. Can you please explain what problem is being resolved with this PR? And, the related eclipse-ee4j/ee4j#71? Thanks. |
@kwsutter sure Objective How
On future new releases of your projects that did such a config, Reproducible Central will try to rebuild and check that the reference "official" build result can be effectively reproduced bit for bit, proving that the objective is attained = binaries that everybody downloads can also be rebuilt from sources; there is no hidden trick between source and binaries For Jakarta EE reference binaries, I think this is something that has even more value than any other projects |
@kwsutter @starksm64 This definitely has value and needs to be merged. |
Signed-off-by: Hervé Boutemy <hboutemy@apache.org>
PR rebased to ease merge |
@ivargrimstad Is there anything precluding this from being merged? thank you! |
I don't think this PR is necessary any longer as it is fixed by the parent pom. |
Can we go ahead and close it then? |
Fixed by Parent pom |
see https://maven.apache.org/guides/mini/guide-reproducible-builds.html
this will permit to add the next release to https://github.com/jvm-repo-rebuild/reproducible-central
once eclipse-ee4j/ee4j#71 is merged and parent upgraded, the
project.build.outputTimestamp
will be updated automatically during release