Currently the only way I know is to use the enforcer plugin (but a version newer than 1.0-alpha-3) with the require plugin versions rule enabled. Then just repeatedly call mvn validate and it will keep on telling you what plugins are missing versions.
I think the plan is to add the functionality to the enforcer or the help plugin, so that you'd have something like mvn enforcer:display-plugin-versions or mvn help:display-plugin-versions I agree that the release plugin should insert the plugin versions. I think this is the idea behind the generate release poms option, but I have not been able to get that option to work how I think it should work -Stephen On Thu, Feb 14, 2008 at 4:30 AM, Trevor Torrez <[EMAIL PROTECTED]> wrote: > I would like to second this sentiment. Is there a plugin that can add > the current plugin version information to the pom? I also definately > think this information should be added to poms processed with the > release plugin (if it isn't already). > > Thanks > > On Jan 29, 2008 5:49 PM, Joerg Hohwiller <[EMAIL PROTECTED]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > | Hi Jörg, > > Hi Stefan, > > | > > | this is also what I see here (see my post about "M2 multi-project site > > | build is broken"). > > | All tests are run for each project in the reactor. I think we could > file > > | an issue for each of the affected plugins, but this seems more like a > > | maven generic issue. Something was "fixed" with devastating effects > for > > | a lot of plugins. What maven version are you using? > > I am using maven 2.0.8 > > Everything works fine if I explicitly set the version of the > > surefire-report-plugin to 2.3 and goes wrong if I use 2.4 > > I did not have the same problem with other plugins. > > Could you track this down? > > Though I know that the latest site-plugin is buggy as well as the latest > > javadoc-plugin. But this are other problems. > > If you want freedom with maven you need to define the versions > > of all plugins explicitly in your toplevel pom. That is what I learned > in a > > bloody bad lessen with maven. The plugin developers often do not know > the impact > > of releasing buggy plugins. There are thousands of maven users that > suddenly > > have a broken build and no idea what is wrong. > > I am using maven from the early days now and switched to maven2 over 2,5 > years > > ago. With maven2 I want to build my code and the project website. > > The site of a multi-project build was a problem for years and even > though > > patches are attached to jira for fixing related plugins such as > cobertura it is > > still not fixed. Sometimes you need to be patient. However maven2 is > excellent > > already and I have big hopes for maven 2.1 all that is going on with > mojo, etc. > > After a lot of pain with maven1 I am happy to see a product with a > design and > > a concept. Thanks to all the great workers of the maven team! > > | > > | Stefan > > > > Regards Jörg > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.5 (GNU/Linux) > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > > > iD8DBQFHn62GmPuec2Dcv/8RAtzeAJ92rvs3JmZmkseghuWYW1/N+GsDRQCfXSxI > > 8P1+VCIkc4HEJIKxZjXnZZs= > > =SZo2 > > > > -----END PGP SIGNATURE----- > > > > --------------------------------------------------------------------- > > 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] > >
