commit | 94eb5829e404eea9109baea6a1455012e936d340 | [log] [tgz] |
---|---|---|
author | Petr Široký <petr.siroky@pm.me> | Wed Feb 15 20:49:40 2023 +0100 |
committer | Slawomir Jaranowski <s.jaranowski@gmail.com> | Mon Jun 05 23:21:01 2023 +0200 |
tree | e29baea5d4161c436baa0347f148a1fbd69153af | |
parent | 9f821e9be13810b8938cf3ac953a24471373f956 [diff] |
[MCOMPILER-391] Use dep mgmt to resolve annotation processors and their deps * dependency managemet can be used for two slighty difference use cases (when it comes to annotation processors): -- getting the version of the top-level processor path elements -- passing the list of managed dependencies to maven-resolver when resolving the whole processorpath These two can be combined, so there is total of 4 valid combinations (some of them make more sense than the others, but generally there is no reason to not support all of them) * using dependency management when resolving transitive dependencies of annotation processors is something that may or may not be desired. For that reason, there is a new flag that explicitly enables this behavior, while default is to _not_ use dependency management (the current behavior)
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.