[
https://issues.apache.org/jira/browse/HBASE-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508169#comment-16508169
]
Mike Drob commented on HBASE-13583:
-----------------------------------
My last patch before I decide to table this for some time.
We can drop the rb source files from the jar we produce, and put that shell jar
on the jruby load path (it's already on the classpath, I think) and try to load
classes out of it. I'm doing something wrong, still, but this all feels like it
_should_ work, so I'm going to take a break. If anybody else wants to pick up
and run with it, then please go ahead.
> 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
> Assignee: Mike Drob
> 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)
