Plugins can be referenced for a project the same way other dependencies
are. If you want to specify the plugin version; site for example:
<dependency>
<groupId>maven</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>1.6.1</version>
<type>plugin</type>
</dependency>
Of course you have to include the remote repository in your repository
list, where the plugin resides.
I'm not sure (maybe one of the developers can tell us) if you specify an
older dependency which one is used... I primarily use this feature to
ensure I'm using a plugin thats been updated since the maven version I'm
using was released.
- Brill Pappin
Buntingster wrote:
[...]
>>>> My question is this: is there any good way to be sure that my developers
>>>> are running in the same maven environment as our build server? By this
>>>> I mean primarily the plugins (and their versions) that are installed.
>>>> This becomes especially critical when we have internal plugins that will
>>>> be modified on a more frequent basis.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
