commit | 36ad0f05ea584d0925d6aeadcc4da92bb1fb9b2a | [log] [tgz] |
---|---|---|
author | Marat Abrarov <abrarov@gmail.com> | Wed Oct 07 19:46:02 2020 +0300 |
committer | GitHub <noreply@github.com> | Wed Oct 07 12:46:02 2020 -0400 |
tree | 3771aad3f23e20527ea468cdf99fd215657418e2 | |
parent | 1670e8b5743458ef1c83879776aa160aa10b090d [diff] |
[MEAR-286] Maven project enhancement (#18) * [MEAR-286] - Moved filtering of resources out of run-its maven profile because this filtering is needed not just for integration tests * [MEAR-286] - Support of invoker.it.skip maven property (can be specified in command line) which can be used to skip integration tests utilizing Maven Invoker Plugin, i.e. to run just integration tests utilizing Maven Failsafe Plugin (mvn verify -Prun-its -Dinvoker.it.skip=true) * [MEAR-286] - Moved Maven Resources Plugin configuration out of run-its maven profile because this filtering is performed even without run-its maven profile
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.
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 --check
before committing.[MEAR-XXX] - Subject of the JIRA Ticket Optional supplemental description.
mvn -Prun-its verify
to 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.