michael-o commented on pull request #10: URL: https://github.com/apache/maven-dependency-tree/pull/10#issuecomment-1032363082
> > > > Look here: https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup#MavenEcosystemCleanup-ResolverandMaven > > > > Maven 3.1.1 comes with Aether not Resolver, does this matter? > > > > > > > > > @michael-o I would prefer aligning everything on using resolver, but that would mean moving the requirements to Maven 3.5.x. > > > > > > I don't disagree, in fact I would prefer to move ALL components to 3.5.4 after Maven 4.0.0-alpha-1 has been released, but consider that this is used in many other components, thus forcing them to update as well. :-( > > If we start defining a new API to hide the resolver, this component may simply be deprecated at some point. Who's actually using this component to estimate the impact? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
