commit | 55fa2d7e594afebfde4a7e1d3cec23a2efc63d1d | [log] [tgz] |
---|---|---|
author | Giorgos Gaganis <gaganis@yahoo.com> | Fri Jul 19 15:32:43 2019 +0300 |
committer | Michael Osipov <michaelo@apache.org> | Sat Jun 20 22:21:08 2020 +0200 |
tree | 16d1fbf9106fec15e70c952ce49965f653c142b5 | |
parent | b418a7b743cba519c5e391fc855ec9b92bf639e7 [diff] |
[MRESOLVER-91] Error messages not clear when not reattempting resolution when a previous attempt failed and the failure was cached For users that were not aware or did not understand well the ResolutionErrorPolicy, the error messages that were presented when this policy was enforced, ie a resolution was not reattempted due to a previous failure that was cached, could be difficult to understand. This closes #37
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.[MRESOLVER-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.