On 9 Sep 07, at 8:27 PM 9 Sep 07, Brian E. Fox wrote:
Presumably wouldn't this just mean building plugins/ with the latest candidate 2.1?
This would also be to check new versions of plugins with older versions of Maven. Knowing for certain and being able to test that the prereq is actually required or correct. It would allow to start doing some aggressive automated testing.
If they don't already have Its, then they wouldn't be avail to port to this new location anyway so I'm not sure it makes a huge difference.
Plugins that don't have ITs could simply have a standard configuration. I just want to validate a plugin functions as expected given a set of Maven versions.
If we release a new version of the site plugin, making sure that it works for users who have 2.0.4 deployed for example.
In my case for 2.1 I'm talking about validating that 2.1 still successfully runs all existing plugins.
I need a place to hook into for a plugin is all I'm saying, and in the source tree wouldn't be good enough because I need the configuration that would be used for a particular release of the plugin. So maybe something equivalent to a little archetype that contains a smoke test for particular version of the site plugin, say.
I make a new version of Maven, I grab the site plugin and all its released versions, for each version I have a smoke test packaged up that I can download run and validate the output.
-----Original Message----- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Sunday, September 09, 2007 10:00 PM To: Maven Developers List Subject: Standard location for a plugin smoke test Hi, Just doing some more planning for 2.1 and it would be very advantageous if we could harness many of the ITs created for plugins in a standard way so that we could run a build of Maven against as many plugins as we can get our hands on. I was thinking a standard directory location of a property in the POM pointing at the IT that should be used as the smoke test. We would also need a way to make a little attached artifact of this smoke test so that we have the smoke test for a particular release of a plugin for the future. I'm not sure how we would retrofit this but basically a standard way with a version of maven to test a version of a Maven plugin to make sure we haven't busted it's use. In particular I'm thinking of how to test 2.1 with all the plugins we know to exist and make sure they continue to work under 2.1. Any thoughts? Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com ---------------------------------------------------------- --------------------------------------------------------------------- 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]
Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com ---------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
