You have found a bug or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
This plugin contains
buildinfogoal for Reproducible Builds tooling, to ease reproducing Maven builds that are expected to be reproducible.
The purpose of this goal is:
to generate a buildinfo file from a build, recording fingerprints of output files, as specified in Reproducible Builds for the JVM that will eventually be deployed to remote repository
help rebuilders to check that they local build produces the same Reproducible Build output than the reference build published to a remote repository
To use this plugin, you'll need to build and install from source, or use SHAPSHOT from
mvn verify artifact:buildinfo
Configure the plugin with its
buildinfo goal in your
If reference build is available in a remote repository with predefined id, like
mvn verify artifact:buildinfo -Dreference.repo=central
If reference build is available in a remote repository without predefined id, use its url instead:
mvn verify artifact:buildinfo -Dreference.repo=https://repository.apache.org/content/groups/maven-staging-group/
We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors.
There are some guidelines which will make applying PRs easier for us:
git diff --checkbefore committing.
[MARTIFACT-XXX] - Subject of the JIRA Ticket Optional supplemental description.
mvn -Prun-its verifyto assure nothing else was accidentally broken.
If you plan to contribute on a regular basis, please consider filing a contributor license agreement.
For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in JIRA. In this case, it is appropriate to start the first line of a commit with ‘(doc)’ instead of a ticket number.