Releases: takari/takari-pom
63
62
Minor change compared to 61: removed --batch-mode
from release plugin arguments. Currently no Takari release is automated, and this change is actually going against that, until https://issues.apache.org/jira/browse/MRELEASE-1156 is fixed.
Full Changelog: takari-61...takari-62
61
Parent that uses Lifecycle 2.2.0.
When updating, pay attention to these:
- make sure you have no
takariVersion
property (make sure you inherit 2.2.0 from parent) - update
settings.xml
, servers were renamed totakari.releases
andtakari.snapshots
. Before they weresonatype...
. - prepare your GPG environment, on workstations ideally you should have GnuPG + GPG agent running, Maven Core GPG plugin is used from now on for signing
- Modernizer execution is fixed and now always run. It may report issues and fail the build. It is at your discretion are those applied or ignored.
Full Changelog: takari-60...takari-61
60
Important changes:
- Deploy repositories renamed to
takari.releases
andtakari.snapshots
(adjust settings, before they were "sonatype." prefixed). - Switched to core GPG plugin for signing, as Takari Signing causes issues on modern systems and modern keys (without fix soon available), while core GPG plugin was vastly improved lately (and got BC signer as well).
- Using latest lifecycle, builds are from now on reproducible.
What's Changed
- Bump surefire.version from 3.4.0 to 3.5.0 by @dependabot in #55
- Bump io.takari.maven.plugins:takari-lifecycle-plugin from 2.1.6 to 2.1.7 by @dependabot in #54
- Use latest Lifecycle by @cstamas in #56
Full Changelog: takari-56...takari-60
56
Plugin updates.
Full Changelog: takari-55...takari-56
55
What's Changed
- Bump com.mycila:license-maven-plugin from 4.3 to 4.5 by @dependabot in #40
- Bump io.takari.maven.plugins:takari-lifecycle-plugin from 2.1.4 to 2.1.5 by @dependabot in #38
New Contributors
- @dependabot made their first contribution in #40
Full Changelog: takari-54...takari-55
54
53
Important: this parent now uses Spotless to reformat sources and build will fail if not properly formatted.
To reformat: mvn spotless:apply
and commit local changes.
To apply this parent, you need several commits:
- update parent, reformat and apply licenses, commit
- commit
.git-blame-ignore-revs
in repo root containing (or adding if file present) of hash of that commit above. - and from now on, you must keep sources properly formatted
What's Changed
- Updates to parent by @cstamas in #16
- Update wrapper by @cstamas in #18
- Apply spotless by @cstamas in #17
Full Changelog: takari-52...takari-53
52
Changes:
- using takari-lifecycle 2.1.2
- update plugins (docck dropped, is deprecated, site moved back to stable from M release)
- mvnw to 3.9.5
Full Changelog: takari-51...takari-52
51
What's Changed
- Misc updates by @mosabua in #4
- Make Takari POM understood (re Java level) by tools like IntelliJ Ide… by @cstamas in #7
- Update Takari parent POM by @cstamas in #9
- ci-improvements: update GHA and test on multiple java versions by @ajayk in #10
- Switch to shared GH actions by @cstamas in #11
- Update POM w/ new plugins by @cstamas in #12
- Update wrapper and Maven by @cstamas in #14
- Update plugins by @cstamas in #15
New Contributors
- @mosabua made their first contribution in #4
- @cstamas made their first contribution in #7
- @ajayk made their first contribution in #10
Full Changelog: https://github.com/takari/takari-pom/commits/takari-51