On 9 Sep 07, at 8:24 PM 9 Sep 07, Brett Porter wrote:
Sorry, not quite grokking this - are you referring to setting up
plugin ITs like the Maven core-its, but on a per-plugin basis?
I think basically we want in each project:
.
`-- src
`-- functional-tests
|-- java
`-- projects
|-- test-project1
| |-- pom.xml
| `-- src
`-- test-project2
|-- pom.xml
`-- src
So, you have in java all the stuff like what we have in integration-
tests, and then the test projects under projects that can be run
independently (but don't verify themselves). I think this is pretty
much consistent with the assembly plugin?
Then in the parent project, we have a profile that enables this
standard layout, and we probably need a way to configure them to
run against either a particular Maven version (M2_HOME, forked), or
using the embedder.
This should allow assembling a test suite that can pull in plugins
from multiple sources (like mojo.codehaus) that follow the same
pattern.
Is that sort of what you were thinking of?
In addition the set of test would have to packaged up so that they
could be retrieved for testing. For each release we will need the
tests as they might change according to configuration or
functionality changes in the plugin. I need a configuration of how
that version of the plugin was used. It would most likely be an
archetype that is created and deployed. How the matrix is execute
will not be hard to do, but we need to start collecting the test
projects and even retrofitting some plugins at least a couple
versions back as this would be the only real way to validate 2.1
actually runs them so that we find the problems before users do.
- Brett
On 10/09/2007, at 11:59 AM, Jason van Zyl wrote:
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]
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
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]
