> > > > I have always had concerns about plexus being pretty much only adopted by > > Maven as far as I can see, and essentially being a maven core component, > > except it isn't > > +1 > > Guice allready as its own large community of users and maintainers. > It's a general 'purpose' API. > > Aether is new, Maven related and need to create its own community. > Why not moving it to ASF as a Maven subproject ? > > +1 for Guice
As discussed here [1], Guice would help a lot integrating nicelly Maven3 into Hudson. It also has a larger user base and doc than Plexus, and has been proposed for a while on this ML as a replacement. The Git branch is also avialable for testing for a while +0 for Aether. It looks technicaly nice according to the code sample [2]. I just share the concern about a major component beeing outside Maven SCM. [1] http://maven.40175.n5.nabble.com/Maven3-with-guice-was-Re-Maven-3-tests-td219507.html#a219507 [2] http://github.com/sonatype/sonatype-aether/blob/master/aether-demo/src/main/java/demo/RepoSys.java Nicolas