> -----Original Message-----
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]]
> Sent: 16 June 2002 07:59
> To: Turbine Maven Developers List
> Subject: Re: New Clover plugin
>
> On Sun, 2002-06-16 at 01:17, [EMAIL PROTECTED] wrote:
> > I'd be happy to talk to the guys @ Cortex about a $0 license for us
-
> > they're in my city :)
>
> Even though it would be $0 for us, I'm not particularly keen on Maven
> being a vehicle for the Clover revenue stream.
>
> David Peugh has been working on integrating quilt and I think we
should
> support that effort as it's an Apache style license and people using
> Maven wouldn't be forced into purchasing a license as they would be if
> using Clover.
Jason, I'm keen on having a completely free and open source test
coverage tool for Maven. The problem is not there. I have tried to use
Quilt several times and:
1/ I don't think it can generate cover coverage for J2EE applications on
which you run logic unit tests, integration unit tests and functional
unit tests. If I remember correctly, it is using a special classloader
which makes it unusable with application servers. I may be wrong, please
correct me.
2/ I don't think it is near what a useful test coverage need to produce.
For example, you cannot see if you have covered this branch of code or
not.
3/ I need the coverage tool to work across projects, i.e. each project
enriches the coverage information.
So in my opinion Clover is way ahead of Quilt in term of usability and
features. But maybe Quilt has improved a lot recently and everything
I've said is now obsolete ? (I would really like this to be the case!).
>
> I definitely think the integration of a coverage tool is important
which
> is why I have been working with David Peugh on BCEL and Quilt from the
> very start. He's been working on the some nasty classloader issues
(Bob,
> you might want to talk to David about the wacky Ant classloader issues
> you're having with Junit) but the first shot at Maven integration is
> done. David sent me the first attempt but I'm jumping on a plane
> tomorrow so I won't be able to do anything. I asked that David make
the
> attempt soon as I would rather encourage the use of Quilt over Clover.
>
I would rather see a library of plugins and let uses choose which plugin
they want to use. One size will never fit all when we start doing more
complex stuff.
I'm going to try making the Clover plugin completely transparent WRT
other plugins.
> Clover looks great and I think the Cortex folk would love to keep us
> happy and let us do the work integrating Clover but the licensing
still
> sucks. Which is why David started Quilt while working on his projects
at
> DARPA because the cost of coverage tools is just ridiculous.
>
> Did the Clover people say how much people would have to pay in order
to
> use it with their projects? Something like: free for OSS projects,
> otherwise your first born.
Don't know.
-Vincent
>
> > --
> > dIon Gillard, Multitask Consulting
> > Work: http://www.multitask.com.au
> > Developers: http://adslgateway.multitask.com.au/developers
> >
> >
> >
> >
> > "Peter Lynch" <[EMAIL PROTECTED]>
> > 06/16/02 02:27 PM
> > Please respond to "Turbine Maven Developers List"
> >
> >
> > To: "Turbine Maven Developers List" <turbine-maven-
> [EMAIL PROTECTED]>
> > cc:
> > Subject: Re: New Clover plugin
> >
> >
> > Here is a convo I had with someone at Clover headquarters about
> licensing.
> > He
> > mentioned Maven integration before I did, so maybe he is on this
list ;-
> ):
> >
> > -------8<----------
> >
> > Hi Peter,
> >
> > > Sorry, but I am missing something. What about if a commercial
> > > company wants to just 'use', not develop the open source
> > > project which has freely licensed Clover?
> > > The open source project by it's license requires no payment
> > > in this case. Will the commercial company need a seperate
> > > clover license costing $125.00 in this case?
> > >
> >
> > My apologies - we haven't explained ourselves very well.
> >
> > As an example, consider the Maven open source project. Maven could
> obtain
> > a
> > $0 Clover license. This would allow the Clover binary to be
distributed
> > with
> > the source distribution of Maven, for the sole purpose of
contributing
> to
> > the open source development of Maven.
> >
> > If a commercial company downloads Maven, and uses it to manage the
build
> > of
> > their own project, they would not be licensed to
> > use Clover for their project. They would indeed need a separate
Clover
> > license.
> >
> > Licensing for Clover is yet to be finalised. Our goal is to make
Clover
> > freely available for open source projects to use, while still
providing
> us
> > with some income from commercial users to support ongoing
development of
> > Clover. We welcome all feedback on how we can better achieve this
> balance.
> >
> > Regards,
> > -Brendan
> >
> > ----
> > Brendan Humphreys
> > Senior Software Engineer
> > Cortex eBusiness
> > http://www.cortexebusiness.com.au
> >
> > ----------8<----------------
> >
> > -Peter
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "bob mcwhirter" <[EMAIL PROTECTED]>
> > To: "Turbine Maven Developers List" <turbine-maven-
> [EMAIL PROTECTED]>
> > Sent: Saturday, June 15, 2002 12:09 PM
> > Subject: Re: New Clover plugin
> >
> >
> > >
> > > > 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).
> > >
> > > +1 if we can get definite clue as to license issues.
> > >
> > > Do we have lawyers to look at this kind of thing?
> > >
> > > > 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).
> > >
> > > Hopefully maven-ng will make plugins such as this
> > > easier to do.
> > >
> > > -bob
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > > For additional commands, e-mail:
> > <mailto:[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:turbine-maven-dev-
> [EMAIL PROTECTED]>
> > For additional commands, e-mail: <mailto:turbine-maven-dev-
> [EMAIL PROTECTED]>
> --
> jvz.
>
> Jason van Zyl
> [EMAIL PROTECTED]
>
> http://tambora.zenplex.org
>
>
> --
> 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]>
