commit | 3ebb44860673e141e3d5f680df434cd5ac61d46b | [log] [tgz] |
---|---|---|
author | Tamas Cservenak <tamas@cservenak.net> | Fri Jan 12 21:02:37 2024 +0100 |
committer | GitHub <noreply@github.com> | Fri Jan 12 21:02:37 2024 +0100 |
tree | 6f102bb2fc9d9efe347abadd065d7991e5c46d0b | |
parent | 30d2b530f7199bed86a03caf53cf884f68e76376 [diff] |
[MINSTALL-197] Update to parent 41, cleanup (#61) In general perform a cleanup of plugin, apply updates where needed. The plugin now builds against 3.9.x latest, and minimum is left as is (3.2.5). A notable change along that above is removal of "baked in" packaging, now plugin relies completely and only on what project and artifact tells, there is no "if this is POM" check anymore. The new "BOM UT" shows this in action. Has to be noted though, that the UT tests ONLY the plugin, to use BOM packaging you need Maven that knows what it is (Maven 3 w/ extension or Maven 4 that has it OOTB). --- https://issues.apache.org/jira/browse/MINSTALL-197
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.[MINSTALL-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.