Jerome, that link contains information on the strategy I've been using in
the assembly plugin, and it seems to work well (although it's a bit slower,
since it's spawning so many Maven builds). I'm hoping to converge the tools
we're using in the core ITs with those in the maven-component-test-plugin
(used to be maven-plugin-test-plugin), and the maven-invoker-plugin, and
arrive at some single solution (a plugin) that we can use everywhere...but I
haven't even been able to come up with a unified feature list yet.
-john
On 4/15/07, Jerome Lacoste <[EMAIL PROTECTED]> wrote:
On 2/24/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> On 04/01/2007, at 4:32 PM, Brett Porter wrote:
>
> > Jason - any further thoughts on this?
>
> Ping... No is a valid answer :)
>
> I'd like to get your summary put somewhere individuals can pick
> things off to work on - probably a jira project for shared. WDYT?
>
> I'm overcommitted for working on things right now, but I know a
> couple of people are confused about the IT testing, and we've got all
> those chronically broken plugins. Volunteers?
I want to improve the state of IT for the mojos I work with (in
particular in the mojo project). I am particularly interested in doing
it in an sort of official/standard way.
- [ ] We need to standardize on integration testing in general. We
have people going all over the place and it's a disaster.
- [ ] We have too many IT plugins (3)
- [ ] We have too many invokers (5)
- [ ] We have too many verifiers (3)
I've found this:
http://maven.apache.org/developers/committer-testing-plugins.html
Does that represent the current IT strategy 'standard' ? Was that
written after the point above was resolved ?
Cheers,
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
