Hi,
I wanted to write some plugin integration tests today and bumped into
the same problems that others have been articulating - it is currently
unclear what direction a new plugin developer should take. The doc on
the web site is not really complete. Though John had started to set
out a path with the assembly plugin, but it has some limitations that
have led to other efforts. Maven's IT structure (also used for
Surefire) is pretty solid but still has some gaps and isn't suitable
in all scenarios.
So instead of beating the same path, I wanted to capture everything
that's been/being done in one place: http://docs.codehaus.org/display/MAVENUSER/Review+of+Plugin+Testing+Strategies
. I trawled through all the current sites and code to pick out the
features and draw them into a matrix. Links are at the bottom for the
things I considered relevant.
Firstly - does that feature matrix look accurate to everyone involved
in this?
I wanted to use this doc as a baseline for any further discussion and
as a place to capture any output so that we have one path forward -
much like the effort made with the Maven ITs in the past.
It's my expectation that the outcomes would be:
1) a set of test projects that exercise different scenarios using the
plugins available today
2) document how to do so
3) identify areas of duplication, and of potential convergence
4) come up with a list of small, doable tasks that will bring this
about, updating docs as it goes
I'm not aiming for a grand unified theory of testing - there will
always be needs for different types of plugins. However, separated
responsibilities (setup/verification vs execution, for example) will
help, esp. when mapped in through the lifecycle (though with the
caveat that configuring more plugins makes testing less approachable).
But what I do need is to beat a path forward, and the Maven ITs were
not suitable for me - so I wanted to capture the output of my efforts
in some way.
WDYT?
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
