Personally, I found the  the shitty plugin easier to setup than others
plugin.
You just add it in your pom and it works. The counterpart is that there are
many less settings compared to others, but I thing that the ones added to
the shitty plugin are enough for a lot of plugins.
Another thing, why I choosed the shitty is due to the usage of groovy and
not beanshell for init/validation script.
I don't know really well groovy but I can write those script in java. In
beanshell, even if the langage seems to be powerful I didn't want to learn a
new one just to write integration tests.

Arnaud

On Dec 14, 2007 5:50 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote:

>
> >Am I right in thinking that right now it's using the
> >"maven-plugin-testing-harness?"  (I've never understood that either,
> >though I haven't tried very hard.)
>
> Yes. It actually works quite nicely. I'm having issues with not getting
> the error code on windows, but this is a plexus-cli issue and not
> directly related to invoker or the harness.
>
> The harness modifies the pom to change the rev to test. It then builds
> the plugin to a new local repo and then executes all the tests against
> that plugin and repo. The one issue I have with it now is that it isn't
> going to your real local to pull artifacts so it downloads from central
> everytime. This is slower than it should be and doesn't work
> offline...but that's an easy fix: configure the current local repo as a
> repote repo in the test builds.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
..........................................................
Arnaud HERITIER
..........................................................
OCTO Technology - aheritier AT octo DOT com
www.octo.com | blog.octo.com
..........................................................
ASF - aheritier AT apache DOT org
www.apache.org | maven.apache.org
...........................................................

Reply via email to