I might have another usecase in toolchains (http://docs.codehaus.org/display/MAVEN/Toolchains) A toolchain definition that is not part of the default set needs to be added as extension to the build. It's accessed by multiple plugins and therefore it's rather impractical to add it as dependency to each plugin that uses it.
Milos On 9/4/07, John Casey <[EMAIL PROTECTED]> wrote: > > On Sep 4, 2007, at 5:34 AM, Jason van Zyl wrote: > > > The biggest offender are providers posing as extensions: wagon- > > webdav is not an extension, it is a dependency required by the > > deploy plugin. In the exact same way you would specify an SCM > > provider as dependency of the release plugin if you needed, say, > > ClearCase support. These are not general extensions they are > > specifically required by certain plugins and should be defined as > > such to scope their use. Dumping wagon-webdav into the core is not > > very bright considering it's use is limited to the deploy plugin. > > This is an oversimplification. Wagons are also used in resolving > artifacts, and while this is not a useful example WRT webdav, the ftp > or scp wagons could easily be required for resolving > dependencies...which is not a plugin task. > > -john > > --- > John Casey > Committer and PMC Member, Apache Maven > mail: jdcasey at commonjava dot org > blog: http://www.ejlife.net/blogs/john > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
