Mark Hobson wrote: > On 17/01/07, Jörg Schaible <[EMAIL PROTECTED]> wrote: >> What we have is also a plugin displaying a dep tree for one of >> compile/runtime/test dependencies. This is really helpful. > > Do you have this internally? I haven't seen that functionality within > the help plugin.
Yes, it's an own internal plugin. We have info:deps-<scope> Unfortunately it is developed at the office and my employer refused to sign the CCLA. Therefore the code is tainted for contribution :( >> So if you're going to move help:dependencies it might be nice to have 3 >> separate goals: >> >> dependency:compile >> dependency:runtime >> dependency:test > > We could do this with the help:dependencies / dependency:tree using a > -Dscope=xxx. Too much typing for a command you will really use very often once you're used to it. Just make the tree mojo abstract and derive the three different ones that set the scope in the ctor. >> Also a filter is something nice: >> >> dependency:runtime -Dfilter=SNAPSHOT >> >> So only the SNAPSHOT deps are shown in the tree ... > > Sounds good. I'll raise these enhancements against the dependency tree > goal. I'll post tomorrow an output from the command line to demonstrate how it looks like. If your reactor build counts ~100 modules, the filter is quite helpful detecting single artifacts in the dep tree or the SNAPSHOTs you have to release (in which sequence). - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
