THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- A brand new immutable Maven API. Finally Maven gets a proper API, that solves two things: developers of plugins can unlesh all the Maven power without jumping hoops and loops, and for us (Maven developers) even better: the Maven implementation finally gets hidden, we can freely hack away. The idea is that the new Maven API becomes the "only touch point" between Plugins and Maven, so Maven Core should not be hindered to evolve with preserving binary compatibility of it's internals (as they will be not accessible, sealed off). Maven API will be available starting with 4.0.0 release of Maven, and we will offer "transition time" for plugins as first Maven 4.0.x (undefined yet for how long) will support both, "old way written Maven Plugins" (as today) and Maven API. But, once you convert to Maven API, your plugin will have a prerequisite of Maven 4+.
- Default Maven Transport changes from legacy Wagon to more modern Resolver HTTP "native" transport. This immediately has effect of potentially halving the Maven HTTP request counts, as this transport is able to extract hashes from response header, sent by Maven Central and all major MRMs. Protocol is still HTTP/1.1, but we are considering upgrade to HTTP/2 as well. Keep eye on this page https://maven.apache.org/guides/mini/guide-http-settings.html
Minimal Set Of Best Practices
...