On Nov 11, 2012, at 5:49 PM, Hervé BOUTEMY <[email protected]> wrote:
> 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 > Not a real issue, my only thought was that if it is all in one place it might be easier for people to understand. >> >> 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 > Sure. I'm currently working on a new test harness for connectors and trying to ramp up to help Benjamin more on the Aether with the code. The test harness is how I'm starting. > Regards, > > Hervé > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder & CTO, Sonatype Founder, Apache Maven http://twitter.com/jvanzyl --------------------------------------------------------- Selfish deeds are the shortest path to self destruction. -- The Seven Samuari, Akira Kurosawa
