Re: Summer status of planned Resolver releases

2024-08-09 Thread Martin Desruisseaux
Le 2024-08-09 à 17 h 01, Tamás Cservenák a écrit : Resolver 1.9.22 and 2.0.1 are out, next are upcoming Maven releases... please keep eye and review PRs (for both, if possible) If it includes Maven 4, can we call it "beta" again?     Martin

Re: Summer status of planned Resolver releases

2024-08-09 Thread Tamás Cservenák
Howdy, Resolver 1.9.22 and 2.0.1 are out, next are upcoming Maven releases... please keep eye and review PRs (for both, if possible) Thanks T On Fri, Aug 2, 2024 at 11:29 AM Tamás Cservenák wrote: > Howdy, > > just a heads up: we have some nice resolver (memory consumption) > improvements that

Re: [Maven Artifact Resolver] Different dependency resolution results

2024-08-09 Thread Tamás Cservenák
Just some details: "tweak" == added some logging to method > DependencyResult retrieve(List jackDependencies) and basically your List is unstable for the same project. And dependency ordering do matter (a LOT). Thanks T On Fri, Aug 9, 2024 at 11:32 AM Tamás Cservenák wrote: > Howdy, > > tried l

Re: [Maven Artifact Resolver] Different dependency resolution results

2024-08-09 Thread Tamás Cservenák
Howdy, tried locally, and I think I got it. But, by tweaking your code, I spotted that it is your input that is unstable (different), and hence Resolver comes up with different output as well. Make sure you feed the same input (we talk about the same test case, so project is same) for the same pro

Re: [Maven Artifact Resolver] Different dependency resolution results

2024-08-09 Thread Tamás Cservenák
Howdy, How could I reproduce this locally? T On Sat, Jul 20, 2024 at 1:28 PM Nick Hensel wrote: > Hi, > > I'm resolving dependencies with the help of Maven Artifact Resolver > (2.0) and I have an issue where resolved (transitive) dependencies > differ from run to run. Currently I'm using "new