You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by Brian McCallister <mc...@forthillcompany.com> on 2004/04/20 15:30:54 UTC
Clover
After playing some, and being very impressed, with Clover I asked for a
license for OJB and they happily donated one for us.
Any objections to me adding this?
Clover basically tests unit test coverage.
-Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Clover
Posted by Robert Sfeir <ro...@codepuccino.com>.
Hum, interesting issue, I wonder if they're aware of that, otoh, their
trial download doesn't expire. I have a full license for codepuccino
stuff too, but we don't have any public projects yet, so I haven't hit
that issue.
R
On Apr 20, 2004, at 6:59 PM, Brian McCallister wrote:
> They are allowed to use it on OJB -- I should probably contact the
> Clover people and verify that they don't mind us plugging the jar into
> cvs. I don't think they will though.
>
> We won't have any dependency on it, just use it for unit tests.
>
> -Brian
>
> On Apr 20, 2004, at 6:50 PM, Antonio Gallardo wrote:
>
>> Brian McCallister dijo:
>>> After playing some, and being very impressed, with Clover I asked
>>> for a
>>> license for OJB and they happily donated one for us.
>>>
>>> Any objections to me adding this?
>>
>>> Clover basically tests unit test coverage.
>>
>> A question how is this related to our users? Are our users allowed to
>> use,
>> redistribute, it according with the ASF 2.0 license?
>>
>> Best Regards,
>>
>> Antonio Gallardo
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Clover
Posted by Antonio Gallardo <ag...@agssa.net>.
Thomas Dudziak dijo:
> On Wed, 21 Apr 2004, Antonio Gallardo wrote:
>
>> Robert Sfeir dijo:
>> > I think that Thomas has a point. There is nothing wrong with just the
>> > lead developers on OJB having the necessary files to run checks on
>> code
>> > coverage, after all, if someone submits a new test, and they can't
>> > check it in, one of the developers will have to do it, and hence they
>> > can run the code coverage test, and post the report on the wiki site
>> so
>> > others can see what is still needed.
>> >
>> > I concur that it doesn't need to be checked into CVS.
>>
>> Not sure. The code must be open, that include the test units.
>
> You misunderstood me. I was merely talking about the clover runtime
> (library, program, whatever) which we don't own but are allowed to
> use within OJB. The unit tests it checks (which are not tied in any
> way to clover AFAIK) as well as any necessary clover settings files
> are/should be public in the CVS.
OK. That means people without Clover can be able to run tests?
Best Regards,
Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Clover
Posted by Antonio Gallardo <ag...@agssa.net>.
Robert Sfeir dijo:
> I think that Thomas has a point. There is nothing wrong with just the
> lead developers on OJB having the necessary files to run checks on code
> coverage, after all, if someone submits a new test, and they can't
> check it in, one of the developers will have to do it, and hence they
> can run the code coverage test, and post the report on the wiki site so
> others can see what is still needed.
>
> I concur that it doesn't need to be checked into CVS.
Not sure. The code must be open, that include the test units.
Best Regards,
Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Clover
Posted by Robert Sfeir <ro...@codepuccino.com>.
I think that Thomas has a point. There is nothing wrong with just the
lead developers on OJB having the necessary files to run checks on code
coverage, after all, if someone submits a new test, and they can't
check it in, one of the developers will have to do it, and hence they
can run the code coverage test, and post the report on the wiki site so
others can see what is still needed.
I concur that it doesn't need to be checked into CVS.
R
On Apr 21, 2004, at 7:29 AM, Thomas Dudziak wrote:
> On Wed, 21 Apr 2004, Brian McCallister wrote:
>
>> Looks like Jakarta-Commons is using Clover as well.
>
> But do they have it in their CVS tree ? Wouldn't it be sufficient that
> one/all developers have it locally and run it in frequently, say, with
> a
> modified build-target that also runs clover whenever the junit target
> is
> run ?
> Personally I'd rather not make software publically available that is
> only
> licensed for the use within OJB (as opposed to the use within projects
> that also use OJB).
>
> Tom
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Clover
Posted by Thomas Dudziak <to...@first.gmd.de>.
On Wed, 21 Apr 2004, Brian McCallister wrote:
> Looks like Jakarta-Commons is using Clover as well.
But do they have it in their CVS tree ? Wouldn't it be sufficient that
one/all developers have it locally and run it in frequently, say, with a
modified build-target that also runs clover whenever the junit target is
run ?
Personally I'd rather not make software publically available that is only
licensed for the use within OJB (as opposed to the use within projects
that also use OJB).
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Clover
Posted by Brian McCallister <mc...@forthillcompany.com>.
Looks like Jakarta-Commons is using Clover as well.
-Brian
On Apr 20, 2004, at 11:29 PM, Robert Sfeir wrote:
> www.thecortex.net/clover
>
> This is what clover is. The only dependency is for checking for how
> much unit test coverage you have for your code, so you can make sure
> that you hit some high percentages of tests v/s code ratio, and make
> sure your whole app is well tested.
>
> OJB will not require clover to run at all. Clover is only there to
> compile your code with for coverage statistics, and that's it. When
> you compile the project with Clover, it inserts 'check points' to
> match up unit tests with methods etc... Then it returns a full report
> of what code is covered, what code is not. As you write unit tests
> you can monitor the progress of your code coverage over time, and know
> where you're still weak, and where you excel.
>
> You can of course always compile the code without Clover, and nothing
> would be different.
>
> HTH.
> R
>
> On Apr 20, 2004, at 9:06 PM, Antonio Gallardo wrote:
>
>> Brian McCallister dijo:
>>> They are allowed to use it on OJB -- I should probably contact the
>>> Clover people and verify that they don't mind us plugging the jar
>>> into
>>> cvs. I don't think they will though.
>>>
>>> We won't have any dependency on it, just use it for unit tests.
>>
>> In fact I don't know what is Clover and why is cool.
>> My mail is just a reminder to avoid any posible lock-in of OJB. If
>> there
>> are concerns, I will recommend you to contact license mail list for
>> this.
>>
>> Best Regards,
>>
>> Antonio Gallardo
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Clover
Posted by Robert Sfeir <ro...@codepuccino.com>.
www.thecortex.net/clover
This is what clover is. The only dependency is for checking for how
much unit test coverage you have for your code, so you can make sure
that you hit some high percentages of tests v/s code ratio, and make
sure your whole app is well tested.
OJB will not require clover to run at all. Clover is only there to
compile your code with for coverage statistics, and that's it. When
you compile the project with Clover, it inserts 'check points' to match
up unit tests with methods etc... Then it returns a full report of what
code is covered, what code is not. As you write unit tests you can
monitor the progress of your code coverage over time, and know where
you're still weak, and where you excel.
You can of course always compile the code without Clover, and nothing
would be different.
HTH.
R
On Apr 20, 2004, at 9:06 PM, Antonio Gallardo wrote:
> Brian McCallister dijo:
>> They are allowed to use it on OJB -- I should probably contact the
>> Clover people and verify that they don't mind us plugging the jar into
>> cvs. I don't think they will though.
>>
>> We won't have any dependency on it, just use it for unit tests.
>
> In fact I don't know what is Clover and why is cool.
> My mail is just a reminder to avoid any posible lock-in of OJB. If
> there
> are concerns, I will recommend you to contact license mail list for
> this.
>
> Best Regards,
>
> Antonio Gallardo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Clover
Posted by Antonio Gallardo <ag...@agssa.net>.
Brian McCallister dijo:
> They are allowed to use it on OJB -- I should probably contact the
> Clover people and verify that they don't mind us plugging the jar into
> cvs. I don't think they will though.
>
> We won't have any dependency on it, just use it for unit tests.
In fact I don't know what is Clover and why is cool.
My mail is just a reminder to avoid any posible lock-in of OJB. If there
are concerns, I will recommend you to contact license mail list for this.
Best Regards,
Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Clover
Posted by Brian McCallister <mc...@forthillcompany.com>.
They are allowed to use it on OJB -- I should probably contact the
Clover people and verify that they don't mind us plugging the jar into
cvs. I don't think they will though.
We won't have any dependency on it, just use it for unit tests.
-Brian
On Apr 20, 2004, at 6:50 PM, Antonio Gallardo wrote:
> Brian McCallister dijo:
>> After playing some, and being very impressed, with Clover I asked for
>> a
>> license for OJB and they happily donated one for us.
>>
>> Any objections to me adding this?
>
>> Clover basically tests unit test coverage.
>
> A question how is this related to our users? Are our users allowed to
> use,
> redistribute, it according with the ASF 2.0 license?
>
> Best Regards,
>
> Antonio Gallardo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Clover
Posted by Antonio Gallardo <ag...@agssa.net>.
Brian McCallister dijo:
> After playing some, and being very impressed, with Clover I asked for a
> license for OJB and they happily donated one for us.
>
> Any objections to me adding this?
> Clover basically tests unit test coverage.
A question how is this related to our users? Are our users allowed to use,
redistribute, it according with the ASF 2.0 license?
Best Regards,
Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Clover
Posted by Robert Sfeir <ro...@codepuccino.com>.
Clover is indeed amazing.
Run it via ant task of course :-)
R
On Apr 20, 2004, at 9:30 AM, Brian McCallister wrote:
> After playing some, and being very impressed, with Clover I asked for
> a license for OJB and they happily donated one for us.
>
> Any objections to me adding this?
>
> Clover basically tests unit test coverage.
>
> -Brian
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org