I've relied on dependency:tree a lot to solve my dependency problems too (mainly when trying to figure out why there's that extra commons- logging-1.0.3.jar in my WAR file when I'm not using it).
Having said that, there's never ever anything wrong with being able to generate pretty pictures to show your clients/management. :) On May 5, 6:14 am, d...@happygiraffe.net (Dominic Mitchell) wrote: > On Mon, May 04, 2009 at 02:20:32AM -0700, jvb wrote: > > > I once wrote a maven plugin which represents the dependencies as a UML > > diagram, exported to <a href="http://en.wikipedia.org/wiki/ > > XML_Metadata_Interchange">XMI</a>. XMI was nice for me because I could > > then analyze the dependencies in UML tools that can read XMI (I used > > magic draw). > > > Don't know if this plugin still works with today's maven release > > though, haven't used it for a while now. > > >http://janvanbesien.blogspot.com/2008/04/maven-dependency-viewer.html > > Both m2eclipse and the NetBeans maven support can create graphs from > POMs. Frankly I don't find it all that useful. mvn dependency:tree > (and the m2eclipse "Dependency Hierarchy" view) seem more useful to me. > In that they've actually helped me to solve problems. :) > > -Dom --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
