> Henri > > I kinda hoped to hear what kind of features you wanted to see and not what > you found in some other tool. I am sure there are bigger possibilities then > things like someone else is implemented. So, please be creative. :-)
Hum correct :) Just take the average eclipse user (not a maven user). He (she) find 'dependencies by looking at MAVEN CLASSPATH. What we be fine is too see : - direct dependencies - dependencies of dependencies - a different color/icon for test/provided dependencies - dependencyManagement effect on required artifacts And just be more creative, seeing them in a tree view in the Maven Classpath It will protect me (and many others) from eclipse users complaining about 'what's that mess with maven, I can't see what is provided by my projects, what is direct required and what came from required :) Regards > regards, > Eugene > > PS: BTW, you probably meant mvn dependency:tree, because dependency:analyze > is checking actually used dependencies by looking that the artifact code... > > > Henri Gomez wrote: > > > Hi Eugene. > > > > Well just take a look at > > http://code.google.com/p/q4e/wiki/DependencyAnalysis - > View Details & > > Terminology. > > > > Very needed since many eclipse users (including my co workers) are not > > very confortable with mvn command line (to make use of > > dependency:analyze. > > > > Regards > > > > > > > > 2008/4/21, Eugene Kuleshov <[EMAIL PROTECTED]>: > > > > > > > > > > > * Graphical dependencies support :) > > > > > > > > > > > Henri, can you please elaborate on this? Eg. what kind of things you > want > > > to be able to do with that. > > > > > > regards, > > > Eugene > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
