On Wednesday 06 December 2006 16:17, Werner Schuster (murphee) wrote: > Ricardo Trindade wrote: > > Hi, > > > > I've been following the rdt mailing list for a while, and I'm glad > > to see that RDT seems to be very active. I'm particularly interested in > > jruby, since I'm using it and the lack of a debugger is a big pain. So > > I'm just wondering if we're getting closer to that objective > > Ricardo, > > I know, I've been writing some JRuby code in the past few weeks, and > debugging with 'puts' is annoying, That's why I looked at the debugger > connection of RDT and JRuby; I believe you saw the discussion on > jruby-user, and the problems (a deadlock in tracing code) are fixed in > the upcoming JRuby 0.9.2. > > Debugging JRuby with RDT is possible (I got it to work under ... let's > say 'lab conditions'). I'm working to bundle this up nicely so it's > possible to just run some JRuby code from RDT and have Debugging "just > work (TM)" if you use JRuby 0.9.2. The RDT debugger uses a Ruby debugger > implementation that doesn't quite work with JRuby (some regex don't > work, and there's some other small stuff). > > I'm working on a JRuby plugin that adds special support for JRuby to RDT. > At the moment I have: > - Code Browsing > clicking on the "org.foo.Bar " in include_class "org.foo.Bar" goes to > the right class; > - Text Hovers > primitive, but docs for fully qualified class names can be shown; > - JRuby Launch support > This is useful in that I hacked RubyInterpreter and CommandExecutor to > use an Extension point; this allows a JRuby CommandExecutor which > sets the JAVA_HOME of the Java process, and - if the started Ruby code is > inside a JDT Java project - sets the CLASSPATH variable (this means, the > launched JRuby process will have the CLASSPATH of the Java project all set > up, so all libs will be visible) > > TODO: > - an action that will allow to a) set the Ruby nature and builder on JDT > projects and b) set Java nature and builder on Ruby projects; > - proper JRuby debugging support; I got a proof of concept for this, but > need to figure out how to integrate it properly; > - maybe some templates for "include_class" or similar constructs; > - tie a bow around it > > > Some of these things need a few small patches to RDT, but I hope to get > this done before the end of the year.
Remember, "Release early and often" is a principle of open source projects. Sounds like you've already got a lot of value... ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rubyeclipse-development mailing list Rubyeclipse-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development
