commit | 4c80e9a3ece1aa6b9c38ece1d0fb65f54155e165 | [log] [tgz] |
---|---|---|
author | Tamas Cservenak <tamas@cservenak.net> | Tue May 16 14:28:18 2023 +0200 |
committer | GitHub <noreply@github.com> | Tue May 16 14:28:18 2023 +0200 |
tree | dfabcc8523271f6afb417ae8914b8d1c338dea0b | |
parent | 6123dfb362afc1ada08c6e658a13aa25772d88d0 [diff] |
[ARCHETYPE-641] Update to parent 39 (#147) Java source changes: * reformat only POM changes: * added plexus annotations and plugin to mgmt as they are gone from parent. To be removed later. * moved out `build.log` from ITs as "create from project" IT was attempting to reuse build.log "live" file and Plexus FileUtils fails sporadically on this IT as after copy it compares in and out file sizes. They may differ, as build.log is "live" log output of current build. GH workflows: * updated to V3 that was backed out as ITs were unstable (fixed above) --- https://issues.apache.org/jira/browse/ARCHETYPE-641
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.[ARCHETYPE-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.