Howdy, This Resolver 2.0.1 release is a bugfix release with several improvements as well: a bugfix in JDK transport, JDK and Jetty transport improvements, and memory usage improvements in collectors and finally IPC named locks (ported from mvnd, module is Java 17+).
Maven 4.x is picking up Resolver 2.x, while Maven 3.x remains at Resolver 1.x lineage. The two major versions, as far as client code goes (Mojos or extensions, using Resolver API as documented), are binary compatible, see [1] aad [2]. Resolver 2.0.1 is to be picked up by the upcoming Maven 4 release. We solved 17 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354901 There are still some issues in JIRA: https://issues.apache.org/jira/projects/MRESOLVER/issues Staging repository: https://repository.apache.org/content/repositories/maven-2176/ Source release SHA512: 94b97928b492cf43ccaa41e0916ca539fd313a524677d61f2a7f786604615b2347af56284b7dad752451dfe05642a9da71e5f94cdecf3f869d52caf9615c672c Staging site: https://maven.apache.org/resolver-archives/resolver-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html [1] https://maven.apache.org/resolver-archives/resolver-LATEST/api-compatibility.html [2] https://maven.apache.org/resolver-archives/resolver-LATEST/upgrading-resolver.html Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1
