google
[rewrite] Add `UpdateMavenWrapper`
related to:
- https://github.com/diffplug/spotless/pull/2636
- https://github.com/checkstyle/checkstyle/pull/17730
- https://github.com/google/error-prone/issues/5195
- https://github.com/google/error-prone/pull/5328
kindly requesting any feedback on this, considering:
- https://github.com/junit-team/junit-framework/pull/5193
it seems there is something for every project to gain upon, thus embracing the conventional principle.
It would be be helpful to provide a summary in PRs and issues of what the goal is, instead of linking to discussions in other issues and PRs, it isn't obvious how this is related to the other linked issues.
Yes, of course, please excuse my shortcomings on this.
I'm wondering if the Maven wrapper is something for this project to consider, like other Google projects and most of the major Maven projects around, using this in regards to the convention principle.
This PR and most of the other related ones demonstrate how each recipe could serve and address a dedicated increment, considered a level up in terms of the same convention principle again.
Starting with some Java migration as the recently pulled changes in the dedicated PR, thanks for this consideration. Going into other details we might find considering the picnic rules.