Ouch... not cool... Aether apparently has a very similar construct to the one I used see:
https://github.com/sonatype/sonatype-aether/blob/master/aether-api/src/main/java/org/sonatype/aether/graph/DependencyVisitor.java as far as what goes into instantiating everything you need to run it, I don't know yet. But I guess I need to update my enforcer rule to use Aether Api. I'm more than a little shocked at problem. Some point over the weekend I'll dig through the mailing lists to see what if anything is planned to be done about this. Plan: Maybe we should construct a cleaner api though. One that could wrap maven-dependency-tree in maven 2.2.1 and use aether in 3.0. It should be a very clean api (nothing but interfaces) and have two implementation, one over each implementation. It's a good sign that this visitor pattern made it through two different implementation. It's very bad that it wasn't made portable. I'd be happy to help you with this if you decide to go down this path, and the maven-devs agree that it's probably the best approach. At least, aether has an api jar file. Which could make future changes like this less painful if we rely on it directly. Looks like it has too much in it though, and a good number of implementation class. Which limits it's ability to be decouple parts of maven.... Rex On Fri, Nov 19, 2010 at 9:15 AM, Jesse Glick <[email protected]> wrote: > On 11/18/2010 07:20 PM, Rex Hoffman wrote: > >> it's pretty straight forward if you use some code provided by the >> dependencies library (part of the maven-dependencies-plugin) >> > > Beware that this does _not_ produce the same results as Aether in certain > cases, and there is no apparent plan to fix it: > http://jira.codehaus.org/browse/MSHARED-167 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
