Seems like this is a good time to start the discussion of which gems to install where. There are actually several gems which comprise the "fast" ruby debugger:
1. ruby-debug-base: this is the gem that implements the core debugging functionality and contains the only native code. jruby-debug builds the java platform version of this gem 2. ruby-debug: command line ruby debugger 3. ruby-debug-ide: the ide support for debugging used by NetBeans (and also Eclipse?) Both ruby-debug and ruby-debug-ide depend on ruby-debug-base, which required me to specify 0.9.3 as the version of the jruby-debug gem so the dependencies would work. If we did preinstall, we would need to preinstall both ruby-debug-base (from jruby-debug) and ruby-debug in order for rdebug to work. I haven't had to touch ruby-debug at all as its pure ruby and just worked once we had the jruby-debug version of ruby-debug-base working. We might want to have the build process grab this gem from rubyforge rather than having the ruby-debug gem in our SVN repo. It might eliminate another issue to have these gems preinstalled also. Right now the MRI version of ruby-debug-base is published in the ruby-debug rubyforge project whereas jruby-debug is part of the debug-commons project. In order for jruby-debug to publish the java platform version of ruby-debug-base we would I think need to work with the ruby-debug project guys. I don't think this would be a problem at all, just something else we would need to work out. This is based on my own rather limited understanding of platform specific gems and my reading of rubyforge docs, so if someone has more knowledge here please chime in. On 10/28/07, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote: > > Peter Brant wrote: > > Hi all, > > > > With the exception of post mortem debugging, jruby-debug is now > > complete. Of course, it hasn't gotten much testing and there must be > > a bug or two still lurking or an edge that needs more polish, but > > overall things should be in good shape. > > > > For anybody wanting to try this out, there are a couple of core bugs > > (JRUBY-1286 and JRUBY-1469 for both 1.0.2 and 1.1, plus JRUBY-1475 for > > 1.1) that affect jruby-debug. I'll look at them tonight or tomorrow. > > > > The fix for the most important one (JRUBY-1469) has already been > > applied (but needs a working test case). > > > > Martin -- Could you please post the GEM to rubyforge.org? (I think > > you need to be a project 'admin' for that, right?) It should be ready > > for public consumption. > > So here's a practical question...should we just include this in JRuby > proper? Most platforms include debugging support out of the box; it > would make sense to me to pre-install the jruby-debug gem as part of our > dist. > > Aweoms work guys, I love to see this kind of collaboration. > > - Charlie > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > >
