Am 2024-11-15 um 16:34 schrieb Tamás Cservenák:
Howdy,
This Resolver 2.0.4 release is a bugfix release with some
improvements as well.
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] and [2].
Resolver 2.0.4 is to be picked up by the upcoming Maven 4 release.
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12355229
There are still some issues in JIRA:
https://issues.apache.org/jira/projects/MRESOLVER/issues
Staging repository:
https://repository.apache.org/content/repositories/maven-2246/
Source release SHA512:
9673ba56ce214de09b3f79798f218f2d8534834a692967cbbc7ef56b459435c586b59f61b3618d5ab63f812403ac08f966afbc7bb6f31b66bfb95fc4d65838eb
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
HTTP/2 is now so old, but impls are still buggy. I dare to question
whether it is tremendously better than HTTP/1.1 compared to its complexity.
M
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
