On Sep 19, 2005, at 12:47 PM, Rick Hillegas wrote:
-0 On the grounds that there's no reason to do so, yet. If someone would like to start writing Junit tests, there's nothing to stop them from doing so. If they contributed them to the codebase, I doubt they would be refused. Since we'd need to vote on such a contribution anyway, as it involves a change to current policy regarding checkins, couldn't we just deal with this when the new test code is contributed? andrew |
- Re: VOTE: Require JUnit jar to build Derby, was: JUn... Andrew McIntyre
- Re: VOTE: Require JUnit jar to build Derby, was... Bernt M. Johnsen
- Re: VOTE: Require JUnit jar to build Derby, was... Jean T. Anderson
- Re: VOTE: Require JUnit jar to build Derby,... Dyre . Tjeldvoll
- Re: VOTE: Require JUnit jar to build Derby,... Rick Hillegas
- Re: VOTE: Require JUnit jar to build Derby, was... Jeremy Boynes
- Re: VOTE: Require JUnit jar to build Derby,... Lance J. Andersen
- Re: VOTE: Require JUnit jar to build Derby,... Daniel John Debrunner
- Platforms/jdks on which Derby is tested... Rajesh Kartha
- Re: Platforms/jdks on which Derby i... Rajesh Kartha
- Re: Platforms/jdks on which De... Manjula G Kutty
