Hi all,
I just ran into this while trying to upgrade from jruby 1.1.2 to
1.1.4. I don’t remember seeing anything about this fly by on the list.
Is this an official bug or a change to the expected behavior. Its easy
to work around but if its a bug, I’ll just hold off on the upgrade.
http://jira.codehaus.org/browse/JRUBY-2958
Thanks,
-lenny
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Lenny M. wrote:
Hi all,
I just ran into this while trying to upgrade from jruby 1.1.2 to 1.1.4.
I don’t remember seeing anything about this fly by on the list. Is this
an official bug or a change to the expected behavior. Its easy to work
around but if its a bug, I’ll just hold off on the upgrade.
http://jira.codehaus.org/browse/JRUBY-2958
It’s a bug, thanks for the report. Hopefully for 1.1.5 we’ll have time
to get in a more robust dispatcher for Java methods; the old one was so
bad we ended up ripping the guts out of it and probably missed a few
cases.
I’ve marked it for 1.1.5.
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email