commit | 99c9c06af39438b48faf76b1bcae6f0c1e4f7f79 | [log] [tgz] |
---|---|---|
author | Tamas Cservenak <tamas@cservenak.net> | Wed Apr 17 20:51:40 2024 +0200 |
committer | GitHub <noreply@github.com> | Wed Apr 17 20:51:40 2024 +0200 |
tree | 4dec7d49672475d3ed54202271198745f3134214 | |
parent | b64984abb52a1fb90d3546e96327ca4ca900e345 [diff] |
[MRESOLVER-535][MRESOLVER-538] Add decorator ability to graph dumper; show ranges (#464) Ability to pass in any function that is able to "decorate" the print out of the graph. This should have a follow up Pr that enable/disable (or simply move all into decorators). Also, verbose tree should show use of version ranges, for cases when someone wants to detect them in whole transitive hull. --- https://issues.apache.org/jira/browse/MRESOLVER-535 https://issues.apache.org/jira/browse/MRESOLVER-538
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.