E.L. Willighagen (Egon) wrote:
>>The current version of the CVS does not compile.
>>It will do, however, in a few minutes from now. :-)
>>Please make sure that the CVS is in a clean state and compiles if
>>someone does a clean checkout.
>>In order to ensure this, please to an "ant clean", "ant dist" before yo=
>>actually commit your stuff. This should ensure that the CVS does *at
> That won't help if there are locally files that are not in CVS. I do th=
> clean test' before checking in, but apparently that is not enough...
>>In addition you should run the tests, at least at the end of the day :-=
>>This will ensure that beside the pure compilability you are likely not
>>to have broken any functionality.
>>People can expect that the CVS does compile and is functional.
> The proper way is actually to do a fresh checkout of CVS, just *after* =
> have done the checkin's of the modifications, and *then* do the 'ant cl=
> test' in the new directory... Unfortunately, this is not common practic=
> bacause it's cumbersome, and won't work on a dial up connection...
Right. So the best thing would be to have a small script on SF which=20
does fresh "cvs co" and "ant dist". If this does not compile, we get an=20
email to the list.
I think there even are some systems out there which unify this kind of=20
server side checking, including running the unit test.
Dr. Christoph Steinbeck (e-mail: c.steinbeck@...)
Groupleader Junior Research Group for Applied Bioinformatics
Cologne University BioInformatics Center (http://www.cubic.uni-koeln.de)
Z=FClpicher Str. 47, 50674 Cologne
Tel: +49(0)221-470-7426 Fax: +49 (0) 221-470-7786
What is man but that lofty spirit - that sense of enterprise.
... Kirk, "I, Mudd," stardate 4513.3..