I had issues with 1.8.7 before patch 352. REE was built with something like 33X when we tried to use ree for our buildr work and it kept blowing up... the earlier patchlevel of 1.8.7 also blew up the same way at the time, so somewhere between what REE based off of and patch 352 for MRI 1.8.7 the issue was resolved. We had issues with SSL certs in MRI 1.9 when we tried using that (change in how 1.9 handles SSL). So now we're using jruby 1.6.5. Takes it a moment to pull its bootstraps up, but it's working better with our bastard frankenstein's monster setup anyways... one day I'll be able to go back and rewrite all this crappy wrapped up ant stuff. I keep telling myself that any how.
On Tue, Jan 3, 2012 at 5:59 PM, Antoine Toulme <anto...@lunar-ocean.com>wrote: > Buildr is tested against 1.8.7 in general. We also made sure of > compatibility towards 1.9. > > I always used Buildr with 1.8.7 in production environments. > > Hope that helps. > > Antoine > > On Tue, Jan 3, 2012 at 08:13, Allen Riddle <allenrid...@gmail.com> wrote: > > > All, > > > > I'm just curious what version of Ruby everyone is running Buildr against. > > I ask because I am having a weird deadlock issue with running JUnit > tests > > with ree-1.8.6-20090610 (I had the same problem with MRI 1.8.6 as well). > > There is a reason why I was using an older version of Ruby, but since > I've > > upgraded to 1.9.2 and the problem has gone away. > > >
