Not sure to understand, maybe I miss-used testing-harness :
I set a test POM with just the plugin configuration, so that I can run :
File testPom = new File( getBasedir(),
"src/test/resources/compile.pom" );
Mojo mojo = (Mojo) lookupMojo( "compile", testPom );
assertNotNull( "Failed to configure the plugin", mojo );
mojo.execute();
Right, but then when my plugin has many plexus @component I have to set them
in the test POM as configuration elements, using implementation="XXXStub".
So it seems this NOT to be a real maven build. The EclipsePlugin requires a
MavenProject with many sub-components, that is difficult to setup
Or maybe I missunderstood the use of this plugin ?
Nico.
2007/12/14, Brian E. Fox <[EMAIL PROTECTED]>:
>
>
> >AFAIK, shitty is similar to invoker, but does more : it install the
> current
> >artifact in local repo with version "testing" and invoke a maven build.
> >Seems to be what the invoker it-test do. Shitty alos use groovy scripts
> to
> >test the result.
>
> This is _exactly_ what the plugin testing harness (currently used by the
> eclipse plugin) does.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
