This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The time for having support for 1.9 is here or very close (for after-6.1)
This won't happen for 6.1; we need JRuby to support it in their parser first which won't happen until JRuby 1.2/2.0.
JRuby 1.1.6 with 1.9 support is out. We should bring this for 7.0. I suppose that among others RubyYaccLexer.java has changed a bit more than usually. So might be more works. I do not have enough insight in this area yet[1], so leaving assigned to you. If you do not implement this, I'll have to look into this later. [1] I mean that I understand the patching mechanism of JRuby classes, just that I do not have insight into JRuby classes themselves yet.
PS: if you want by any chance to start on this now, I've already uploaded jruby-src-1.1.6.zip onto hg.netbeans.org/binaries: echo 'D26C2FD55DE02E4A6BF672724204822B0F2DC834 jruby-src-1.1.6.zip' > $NB_SRC/o.jruby/external/binaries-list
I started on it a few weeks back, ran into various snags, tried some other things, and talked to Tom about it -- and here's the future: http://kenai.com/projects/jruby-parser I just talked to Tom and he's going to try to get a first version working soon. One we have that (JRuby's parser and lexer isolated) it should be much easier for us to do regular updates and we'll be completely isolated away from the runtime stuff in the in-IDE processing. (And yes, this means the IRB thing really does have to go away and use proper terminal emulation.)
Sounds great, thanks for the info.
The IDE now uses jruby-parser and 1.9 is hence now supported.