Afair, we have 31 open issues left :) Most of them are old, probably invalid ones.
T On Tue, Jul 2, 2024, 19:28 Michael Osipov <micha...@apache.org> wrote: > Nothing specific, just wanted to make sure. > > On 2024/07/02 15:45:23 Tamás Cservenák wrote: > > Howdy, > > > > I think we cannot have breaking change for several reasons: > > - maven4 (w/ Resolver 2) will still happily execute Maven3 plugins and > > extensions (those compiled against Resolver 1.x) > > - we promised same thing here [1] and here [2] > > > > So for users of resolver "public APIs", the modules API, SPI and UTIL" we > > gave our promise nothing changes (not counting that deprecated things are > > gone, which is IMO okay). > > All the code that uses Resolver upgradied to 2.x (ie. when running in > > Maven4) should be “smooth sailing”: IF you do not depend (directly or > > indirectly) on deprecated classes from Resolver 1.x. > > > > Or you have some issue specifically on your mind? > > > > [1] > > > https://maven.apache.org/resolver-archives/resolver-LATEST/api-compatibility.html > > > > [2] > > > https://maven.apache.org/resolver-archives/resolver-LATEST/upgrading-resolver.html > > > > > > On Tue, Jul 2, 2024 at 5:34 PM Michael Osipov <micha...@apache.org> > wrote: > > > > > Before completing the GA release, did you take a look at the open > issues, > > > are there any which qualify for 2.0.0 *and* require a breaking change > in > > > Resolver? > > > > > > On 2024/07/02 10:06:16 Tamás Cservenák wrote: > > > > Howdy, > > > > > > > > This Resolver 2.0.0 release is a new feature release. 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]. > > > > > > > > We solved 155 issues: > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12352721 > > > > > > > > There are still some issues in JIRA: > > > > https://issues.apache.org/jira/projects/MRESOLVER/issues > > > > > > > > Staging repository: > > > > https://repository.apache.org/content/repositories/maven-2157/ > > > > > > > > Source release SHA512: > > > > > > > > 75c0c8869393ae7a0c3e7c1bb2e1c93352e93165ff4ccfcff7fb785b77989b176e44cd28c142856e1a9884f88dc0bf3a2b40f62ab4064b422089f640816496a2 > > > > > > > > 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 > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
