[
https://issues.apache.org/jira/browse/HBASE-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508830#comment-16508830
]
Mike Drob commented on HBASE-13583:
-----------------------------------
Chatted a bunch with the JRuby team on IRC, apparently jrubyc isn't currently
as useful as we imagined it to be.
bq. right now it doesn't _really_ even compile to bytecode; it's just a .class
file containing a serialized version of our internal representation
which means we'll get neither startup speedup or java method invocation
validation.
> AOT compile our JRuby
> ---------------------
>
> Key: HBASE-13583
> URL: https://issues.apache.org/jira/browse/HBASE-13583
> Project: HBase
> Issue Type: Improvement
> Components: build, scripts, shell
> Reporter: Nick Dimiduk
> Priority: Major
> Attachments: HBASE-13583.patch, HBASE-13583.v2.patch,
> HBASE-13583.v3.patch, HBASE-13583.v4.patch
>
>
> Our Jruby code seems to not keep up well with Java changes. We should
> investigate adding a compilation step for our shell and the rb scripts in bin
> to ensure they're calling methods that exist on classes that exist. This
> looks like as good a starting point as any:
> https://github.com/jruby/jruby/wiki/GeneratingJavaClasses
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
