David Sag wrote:
well i would agree in principle but the maven2 plugin matrix you list is hopelessly out of date, and always has been.
The plugin matrix is meant to be a guide. It does not scale right now and it is hard to keep up to date because it is a manual process. We definitely want to move toward pushing more plugin information during the deployment of the plugin and then our new repository manager can scan for that and index the information and we'll use that to generate the plugin matrix. But we needed to start somewhere and see what kind of information would be good to display and now we can go about working on a generated version.
my current irritation is that i have no idea what the latest versions of most plugins are and what their compatability status with maven 2.0.2
With the generated version of the matrix you will easily be able to see that.
is. I foolishly upgraded to 2.0.2 and now can't get my projects to build properly anymore.
The integration tests we have more then cover the basics. I'm sure your project builds but when you get into using never released plugins like cobertura you're probably going to run into some problems. Optimizing the lifecycle is a general problem right now and a general solution is slated for the 2.1.
Kind regards, Dave Sag
-- jvz. Jason van Zyl jason at maven.org http://maven.apache.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
