Re: [Bodington-developers] Who's Running Cruise Control?

[Jon M. <jo...@te...>]

Thanks Matthew.  I think your Cruise Control must have lost its 
connection with the server some time ago and left a lock.  I've asked 
the sourceforge support people to delete the lock files.

That jar file doesn't need to be compiled with 5.0 - I'll rebuild it and 
upload a replacement.  It's related to my fix for the security hole I 
reported some time ago and that's why I'm currently checking stuff in.  
(I'm not checking in the code that implements the fix - just the code 
that interfaces to it.)

Jon

Matthew Buckett wrote:
> On Sun, Mar 16, 2008 at 1:51 PM, Jon Maber <jo...@te...> wrote:
>   
>> Hi everyone.
>>
>>  Who's running cruise control against the Bodington CVS tree?
>>     
>
> I've got it building automatically from CVS at Oxford.
>
>   
>>  I'm trying
>>  to check in some source code and I'm getting this;
>>
>>  cmd: "cvs"  commit -F "/home/jon/.crossvc/tmp.F1Pe9O" "BodingtonURL.java"
>>  cvs commit: [13:37:58] waiting for bodcruz's lock in
>>  /cvsroot/bodington/bodington/src/org/bodington/util
>>
>>  It looks like cruise control has stalled and has a lock open.
>>     
>
> I've had a look and there isn't any CVS command still running by
> cruisecontrol. So if the lock still exists you can remove them.
>
> http://www.network-theory.co.uk/docs/cvsmanual/Concurrency.html
>
> BTW - The cruise control build is currently failing because
> lib/cookiecutter.jar is compiled as a JDK 1.5 class and it was the
> case that Bodington was compatible with 1.4. Personally I think 1.5
> code should be ok now, but Oxford isn't currently running on JDK 1.5
> but will be in the not too distant future.
>
>