Parent poms with versions set in their pluginManagement section makes
absolute sense. Of course no list is complete, and it needs to be
maintained, but in most cases you are better off using an old version of a
plugin than using an unknown latest version. Here's what I have in one
parent pom:
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<version>1.1</version>
<dependencies>
<dependency>
<groupId>ant</groupId>
<artifactId>ant-nodeps</artifactId>
<version>1.6.5</version>
</dependency>
<dependency>
<groupId>ant</groupId>
<artifactId>ant-optional</artifactId>
<version>1.5.3-1</version>
</dependency>
<dependency>
<groupId>ant-contrib</groupId>
<artifactId>ant-contrib</artifactId>
<version>1.0b2</version>
</dependency>
</dependencies>
</plugin>
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-1</version>
</plugin>
<plugin>
<artifactId>maven-clean-plugin</artifactId>
<version>2.1</version>
</plugin>
<plugin>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>2.1</version>
</plugin>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.0.1</version>
</plugin>
<plugin>
<artifactId>maven-eclipse-plugin</artifactId>
<version>2.4</version>
</plugin>
<plugin>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.3</version>
</plugin>
<plugin>
<artifactId>maven-install-plugin</artifactId>
<version>2.1</version>
</plugin>
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<version>2.1</version>
</plugin>
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.0</version>
</plugin>
<plugin>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-7</version>
</plugin>
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<version>2.2</version>
</plugin>
<plugin>
<artifactId>maven-site-plugin</artifactId>
<version>2.0-beta-5</version>
</plugin>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.2</version>
</plugin>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.0.2</version>
</plugin>
</plugins>
</pluginManagement>
Kalle
On 11/14/07, Erez Nahir <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> We are having some build stability issues from time to time when
> developers remove local repositories. From time to time, maven fails to
> download plugin...
> Another difficulty we have is control on plugin versions, some plugins
> listed in some files and when one would like to change plugin version,
> he/she need to go through bunch of files, find and replace all versions
> of same plugin (antrun-plugin for example).
>
> Currently we do not have any pluginManagement section and we also do not
> list some plugins (maven-site-plugin for example) in our pom.
>
> We have big project with 10s of components/pom.xml files and I was
> thinking to add pluginManagement as well as adding all default plugins
> with current version.
>
> Does any document list all default plugins and a recommended list of
> plugin management?
> Can someone share his/her list if exist?
>
> Thanks,
> Erez.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
