commit | 3f95d39f166809bc1a2bb0b2fa62c190e8d2a9f7 | [log] [tgz] |
---|---|---|
author | Petr Široký <petr.siroky@pm.me> | Mon Jan 30 01:51:40 2023 +0100 |
committer | GitHub <noreply@github.com> | Mon Jan 30 10:51:40 2023 +1000 |
tree | f61eb0bd57b8d8179a5f6bc4ccd2cca170d30c99 | |
parent | aab8416877222af44695f65797c18adad55a1349 [diff] |
[MCOMPILER-503] Resolve all annotation processor dependencies together (#170) * [MCOMPILER-503] Resolve all annotation processor dependencies together * resolving the anootation processor paths in multiple requests can easily lead to duplicated dependencies, e.g. if two processors depend on the same transitive dependency. Ultimately, both versions would end-up on processorpath, but of course only one of them would be used (likely dependeing on the order of elements of processorpath) * the previous behavior also did match the general rules of dependency resolution used by Maven itself and other plugins * this may potentially be a breaking change for certain corner cases, if for example some projects mistakenly rely on the order of elemenets in processorpath * [MCOMPILER-503] Extract and reuse annotation-verify-plugin in multiple ITs
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.[MCOMPILER-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.