> -----Original Message-----
> From: Kurt Schrader [mailto:[EMAIL PROTECTED]]
> Sent: 15 June 2002 20:07
> To: Turbine Maven Developers List
> Subject: Re: New Clover plugin
>
>
> I have been using clover lately and it is awesome, although I'm not a
big
> fan of the ambiguous licensing terms.
> +1
same here. I'd really like to make it a real plugin, i.e. against a core
plugin API. Our Maven build site ties all plugins together and it is
hard to add a new plugin without touching something existing.
We are almost there with callbacks and maven-ng but not completely. Is
it possible in maven-ng to completely replace a target from one plugin
and then this new target can be used seamlessly by other plugins ?
-Vincent
>
> -Kurt
>
> On Sat, 15 Jun 2002, Vincent Massol wrote:
>
> > Hi,
> >
> > I have started integrating Clover into Maven. I have actually
something
> > working as demonstrated on http://raccoon.sourceforge.net/new/
(click on
> > "Maven reports" and then on "Test Coverage").
> >
> > I want to know if it is ok to commit that in our CVS ?
> >
> > I have had to modify the build files for core, doc, and test.
> >
> > It is completely transparent (by default a property named
> > maven.compile.clover is set to false, i.e. no test coverage)
> >
> > What remains to do :
> >
> > - ATM you need to put clover.jar in your anthome/lib and as a
dependency
> > in your project. I would like it to be completely transparent for
the
> > project.
> >
> > I'm eager to commit but I wanted to check with you first ... :-)
> >
> > Note: The only "issue" that I can see is that clover is free for all
> > non-commercial projects only (however, Cortex, the company creating
> > Clover seem ok for us to redistribute the clover jar).
> >
> > It is a plugin I'd like to see integrated in Maven as it is the best
> > test coverage tool that I have seen and by far. The problem is that
I
> > don't know how I could write such a plugin with no impact on
existing
> > ones (core, test, doc). The same issue will happen with
> > Jalopy/JRefactory (but it is easier for them as they don't need to
> > modify the compile target, etc).
> >
> > Thanks
> > -Vincent
> >
> >
> > --
> > To unsubscribe, e-mail: <mailto:turbine-maven-dev-
> [EMAIL PROTECTED]>
> > For additional commands, e-mail: <mailto:turbine-maven-dev-
> [EMAIL PROTECTED]>
> >
>
>
> --
> To unsubscribe, e-mail: <mailto:turbine-maven-dev-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:turbine-maven-dev-
> [EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
