The plugin is automatically downloaded and installed instead of to ask to the other developpers to manually install it. It forces the developpers to use THIS release of the plugin for the project.
Arnaud On 2/9/06, Matteo Melani <[EMAIL PROTECTED]> wrote: > Hello, > what is the benefit of including in the project.xml file a dependency > to a plugin? (Besides telling other developers that the build depends on > the plugin) > > For example let say that I include in my project.xml: > > <dependency> > <groupId>codeczar-tomcat</group> > <artifactId>maven-tomcat-plugin</artifactId> > <type>plugin</type> > <version>1.1</version> > </dependency> > > When I run Maven it downloads the .jar file for the plugin in the > repository plugin directory. And then? > > I guess I do not understand the purpose if it. > Anybody can explain this feature? > > Thanks, > -Matteo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
