commit | 45c5bdf03ec25dd1654997bca56f28e0c59c5897 | [log] [tgz] |
---|---|---|
author | Tamas Cservenak <tamas@cservenak.net> | Tue Dec 05 19:55:31 2023 +0100 |
committer | GitHub <noreply@github.com> | Tue Dec 05 19:55:31 2023 +0100 |
tree | 1e751423362b0620045dd43794b8ea7294750947 | |
parent | 9b87550d0b25af64d5b08b5e2fb505ec9ffd34bb [diff] |
Update UTs regarding deprecations (#387) With latest changes there were some deprecations, most notably the default ctor of DRSS. Due that the build started emitting quite some warning messages during build. This is now lowered to 2 warnings for whole build. There is no issue for this, as these changes are all happening in UTs.
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.