Le samedi 10 novembre 2012 18:08:02 Jason van Zyl a écrit : > > 2. plugins or components: using Aether API would mean that it won't work > > with Maven 2 or 3.0. With maven-dependency-tree layer as compatibility > > layer, the problem disappears. But DependencyGraphBuilder API is rather > > limited: any feature requiring an extension to this API would require to > > implement it for Maven 2 + 3.0 + 3.1 + ... > > Are you planning on pushing this back into maven-artifact to make a unified > API? no, I don't see any benefit
> > So I will take that as limiting Aether to the core and the small exception > of the dependency-tree component. I think that keeps everyone happy. I'm happy with it I'd be interested in feedback from others > > The only thing that require special attention is knowing how much Eclipse > > Aether is different from Sonatype Aether, package change taken apart I'm working on maven-aether-provider unit tests to help on that point any help appreciated Regards, Hervé --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
