[
https://issues.apache.org/jira/browse/HBASE-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16505570#comment-16505570
]
Sean Busbey commented on HBASE-13583:
-------------------------------------
that's a problem with the version of [ASM|http://asm.ow2.io/] that must be on
the classpath during the maven invocation. It looks like the [Opcodes
class|http://asm.ow2.io/javadoc/org/objectweb/asm/Opcodes.html] in your
classpath is limited to JDK6 and earlier, but JRuby is expecting 1.7+.
Try adding it as a dependency to the jruby-maven-plugin plugin declaration.
> 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
>
>
> 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)
