Peter Brant wrote:
Hi Martin and Chris,
I'd like to help out with jruby-debug too. To avoid duplication of
effort, are there specific things you guys are working on? Barring
that, I don't have much of a plan besides to poke around, see what
doesn't work, and fix it.
I also do not plan too much. When I have some time for it I just run the
debugger and start to fixing the first thing that bothers me.
I think we could use the debug-commons forum to communicate about what
we are working on or planning to work on. I've just create a new forum:
http://rubyforge.org/forum/forum.php?forum_id=17962
I suppose you need a ruby-forge account to post. Maybe mailing list
would be better(?)
First patch here http://jira.codehaus.org/browse/JRUBY-1286 (actually
a JRuby bug that was preventing exit in rdebug from working).
Thanks a lot of for this. It is actually almost blocker from the
NetBeans QA's point of view (prevents hanging processes). Will try it as
soon as I can.
Regarding BasicLibraryService, does this really help us? We still
need to associate RubyDebugBaseLibrary with a specific name we can't
pick. Or could jruby-debug be packaged as a JAR file and picked up
that way with the standard name?
We need the specific name, but I do not see into this part of code too
much. Seems that you or Chris know more.
(for now, I did change the registerBuiltin() call in my copy to use
reflection so jruby_trunk and jruby-debug can be separate projects)
As soon as you feel you have some bigger chunk of work and you feel that
you will need it more and more :), let me know and I'll add you to the
debug-commons project.
There are more projects on debug-commons and even more plans. So any
contribution is appreciated. Seems that jruby-debug "subproject" could
have two new members so I could work on e.g. DBGp bridge, until somebody
wants to contribute it ;)
Regards,
m.
PS: I'll definitely not get to the jruby-debug until next week
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
