You can define a plugin dependency in your POM.
For example :
<dependency>
<groupId>statcvs</groupId>
<artifactId>maven-statcvs-plugin</artifactId>
<version>2.5</version>
<type>plugin</type>
<url>http://statcvs-xml.berlios.de/maven-plugin/</url>
<properties/>
</dependency>
Arnaud
On Tue, 28 Sep 2004 09:25:13 -0400, Helck, Christopher <[EMAIL PROTECTED]> wrote:
> I don't understand how maven plugins are managed. Suppose I'm working on
> a project and decide that I need to upgrade a plugin. So, I grap the
> latest version of a plugin and install it. Do other people on my team
> also need to install the plugin? Since the project.xml does not list
> plugin dependencies, how does maven know which one to use?
>
> Regards,
> C. Helck
>
> The information contained in this e-mail is confidential. This e-mail is intended
> only for the stated addressee. If you are not an addressee, you must not disclose,
> copy, circulate or in any other way use or rely on the information contained in this
> e-mail. if you have received this e-mail in error, please inform us immediately and
> delete it and all copies from your system.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
