Presumably wouldn't this just mean building plugins/ with the latest candidate 2.1? 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.
-----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]
