Tested Trino build with both JDK 22 and JDK 23-ea and maven build from https://github.com/apache/maven/pull/1460. The previous problem with binary compatibility in one of the plugins we use is gone.
On Fri, Mar 29, 2024 at 1:20 PM Tamás Cservenák <ta...@cservenak.net> wrote: > Howdy, > > Note: This is an eighth (alpha-4 and alpha-9 was scrubbed) preview release > of Resolver 2.0.0, that would allow any downstream consumers to try it out > and adapt. The supplier is aligned with Maven 4.0.0-alpha-13. This resolver > now implements "dynamic scopes" using newly introduced ScopeManager (as > opposed to Resolver 1.x "cemented/wired in scopes"), making Resolver truly > "scope agnostic" (as it is from now on just a matter of scope manager > configuration). Also, a bug fix is there that restores backward binary > compatibility. > > For configuration changes, see > > https://maven.apache.org/resolver-archives/resolver-LATEST/configuration.html > > IF the vote is successful, the staging site will NOT be moved to > https://maven.apache.org/resolver/ but instead will be made reachable from > https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-10/ only. > > The 1.9.18 is still the "latest stable" release of Maven Resolver. > > === > > We solved 11 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12354447 > > There are still some issues in JIRA: > https://issues.apache.org/jira/projects/MRESOLVER/issues > > Staging repository: > https://repository.apache.org/content/repositories/maven-2080/ > > Source release SHA512: > > ba52c431d11adcfbbd2aac088c4ba0bb9c4f864f084047d45ed64fa806ee0625fadd6447cce6f39f05abd493c6f54cc2b6d70740efa6bc994ce694936f6c9e0d > > 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 > > Vote open for 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 >
