I've raised some pull requests to add the Takari maven wrapper.

The Takari maven wrapper is EOL and will be replaced with the Maven
Wrapper when Maven v3.7.0 is released.

I've added the Takari version as maven v3.7.0 is not yet out. I've
been using the Takari maven wrapper for about 4 years now and it has
reduced a lot of maintenance and setup tasks.

- Maven Wrapper is Maven-As-Code
- CI/CD, your docker images or Jenkins slaves no longer need maven pre
installed, so less maintenance tasks
- Developers don't need to pre install maven
- Projects control what version of maven to use, maybe a legacy
project needs v3.3.1 and a newer project needs v3.6.3. A developer
doesn't need to keep changing their PATH, they just use ./mvnw.
- Want to check a new version of maven, just change the properties,
then it can undergo the standard pull request build checks to make
sure the project works with that version.

The first PR I raised was for commons-code and can be found here
https://github.com/apache/commons-codec/pull/58

I've also done similar or;
commons-collections
commons-configuration
commons-io
commons-lang
commons-parent
httpcomponent-client
httpcomponent-core
httpcomponent-parent

John

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to