Mark Hobson wrote: > On 17/01/07, Jörg Schaible <[EMAIL PROTECTED]> wrote: >> 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 :( > > No worries, we have the dependency-tree shared component and > help:dependencies goal to work with now. > >> 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. > > Perhaps, but I was thinking about the number of goals once we > introduce tree and list goals for every scope. Would we name them > dependency:compile-tree, dependency:compile-list, etc.? That's ten > extra goals, I'm not sure if it's easier just to type dependency:tree > -Dscope=compile.
10? I just count 6 instead of two ... only 3 scopes make sense - or? What about: dependency:<scope> -Dtype=<list|tree> then everybody has the possibility to configure a property in his settings for the preferred view type ... [snip] - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
