db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo" <agalla...@agssa.net>
Subject Re: Clover
Date Wed, 21 Apr 2004 11:53:03 GMT
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

View raw message