>This is true, I haven't used dependency:resolve until you mentioned it. I >guess the only difference is that it doesn't show the scope of the >dependencies, but this could be easily resolved.
Heh, actually I just added that feature last night before reading this thread. (mdep-57). >Yeah that was my problem with the multiple goals, it would start to clutter >the plugin usage. I agree list is similar to resolve. Tree could also be >performed by resolve, but just with a different output format. Maybe list >and tree could be synonyms of resolve, implemented as a simple subclass? Definitely subclasses of resolve. I've been trying to layer the abstract classes in such a way that the parameters are as consistent as possible across all the goals, without implementation duplication. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
