This is exactly what the test project in each plugin is for.
Some have them, some don't. Look in the plugin-test directory of a plugin.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
John Casey <[EMAIL PROTECTED]> wrote on 14/12/2003 04:01:20 AM:
> I think properly placed touchstone builds in each plugin to check
> assumptions would be a great idea...it's a mountain of work in its own
> right, but it would also help to enumerate the different configuration
> points that a plugin uses, and what they are used for...
>
> On Fri, 2003-12-12 at 20:00, Christopher W. Farnham wrote:
> > Perhaps there should be a plugin or test of some sort to validate
> > plugins and make sure that they
> > adhere to some basic standards like using ${maven.build.dir} rather
> > than hardcoding to 'target/'.
> >
> > Anyone can write a plugin anyway they want, but this could be a
> > checkstyle type thing to help people out.
> >
> > I'm well aware that a suggestion like this is usually followed by a,
> > "Great idea, you should go ahead and do it." and
> > I might... once I get out from this mountain of work I have. Also
I've
> > only written a few plugins of my own, but nothing
> > too complicated or earth-shattering.
> >
> > Christopher Farnham
> > Senior Consultant at Wrycan, Inc.
> >
> > [EMAIL PROTECTED]
> > http://www.wrycan.com
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
