|
I agree, too, though before I didn't think JSR 223 implementation was not necessary to bundle in JRuby. JSR 223 is a generalized API for many scripting languages, which does not always draw 100% power out from JRuby. So, I wrote the two layers implementation, JSR 223 was on the top of a middle layer. Currently, the preliminary middle layer, JRuby Embed API Although JSR 223 implementation would be a subset of JRuby Embed API, many people want JSR 223 support by JRuby. Why don't we think about this? We have wanted to get 223 in JRuby proper, but to be honest none of us are happy with the current implementation and would like one that we can license according to JRuby's existing licenses and implement the way we want to implement it. We want to work with Yoko to get a new 223 engine built "the right way" and shipped with JRuby before we start including anything and set an expectation on the existing version. So I'll tell ya what...if we can all work together to get a really solid 223 impl built, we would include it in JRuby 1.4 so it's available for everyone. That gives us a hard goal to reach and a deadline for when we'll reach it. Is that acceptable?
Charles Oliver Nutter made changes - 22/May/09 08:19 PM
Fine with me to wait until JRuby 1.4 (but with a high priority!). I have a Java/Jruby app using JSR 223 so I can help testing the new version. jruby-embed landing has added this support!
Thomas E Enebo made changes - 30/Sep/09 04:45 PM
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yes, I agree. Besides being easier, it would also be easier to ensure that the two versions are in sync that way. Too extra needed code is so tiny that there is really no reason for not doing as far as I see it.