If you run your build with the -X option and redirect the output to a file, you can search through it for "plugin" and get a list of the plugins you use along with the current versions it is using.
I use this as a start in building the pluginManagement section. Then you have to do a little research to find out if these versions are the ones you want. I have not found a good way to do that. I start by looking on the maven web site at the list of plugins. This page will list many of the "current" release versions. Then I search through the mailing list to find any complaints about those plugin versions. (There is a lot of clutter/static doing it this way.) If the complaint is justified and I find it to be relevant to my build, I might back off a version on that plugin and, of course, repeat the research. I suspect there is some way to use the list of Jira issues to help with this process. Does anyone have some ideas here for how to find out the best plugin version to use. Additionally, this means that as your project progresses you may need to move to new plugin versions. This comes into play, particularly, if you add some features to your application that require adding features to your build and you find you run up against a bug in a plugin. You can get problems like one I have now. I have to comment out my proxy entry in settings.xml when I am deploying my site (via SCP) because it always uses the proxy and I am SCPing it to a non-proxy location. Then I have to put the proxy back in settings.xml when I build with the dashboard plugin because that plugin comes from the codehaus snapshot repo which I don't don't include in things managed by Proximity. Now, this is a minor problem effecting only the building and deploying of the site. Its not really part of building the application and it doesn't happen on my build server (trust me, I don't want to explain it). But the same sort of stuff can pop up as relates to your build now and then. You can sometimes get rid of the problem by backing off the plugin versions. Thanks. -- Lee On Nov 14, 2007 10:12 PM, Kalle Korhonen <[EMAIL PROTECTED]> wrote: > 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] > > > > > -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
