[
https://issues.apache.org/jira/browse/HBASE-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086015#comment-13086015
]
Chul Kwon commented on HBASE-3873:
----------------------------------
I figured out the problem.
When you give -Dsnappy.prefix=$SNAPPY_BUILD_DIR option, the builder tries to
find libjvm.so in the Snappy directory, not at
$JAVA_HOME/jre/lib/{$OS_ARCH}/server.
Therefore, you need to either fix the source code or simply make a symlink in
the $SNAPPY_BUILD_DIR to your libjvm.so
> Mavenize Hadoop Snappy JAR/SOs project dependencies
> ---------------------------------------------------
>
> Key: HBASE-3873
> URL: https://issues.apache.org/jira/browse/HBASE-3873
> Project: HBase
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.90.2
> Environment: Linux
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Labels: build
> Fix For: 0.92.0
>
> Attachments: HBASE-3873.patch, HBASE-3873.patch
>
>
> (This JIRA builds on HBASE-3691)
> I'm working on simplifying how to use Hadoop Snappy from other based maven
> projects. The idea is that hadoop-snappy JAR and the SOs (snappy and
> hadoop-snappy) would be picked up from a Maven repository (like any other
> dependencies). SO files will be picked up based on the architecture where the
> build is running (32 or 64 bits).
> For Hbase this would remove the need to manually copy snappy JAR and SOs
> (snappy and hadoop-snappy) into HADOOP_HOME/lib or HBASE_HOME/lib and
> hadoop-snappy would be handled as a regular maven dependency (with a trick
> for the SOs file).
> The changes would affect only the pom.xml and the would be in a 'snappy'
> profile, thus requiring '-Dsnappy' option in Maven invocations to trigger the
> including of snappy JAR and SOs.
> Because hadoop-snappy (JAR and SOs) are not currently avail in public Maven
> repos, until that happens, Hbase developer would have to checkout and 'mvn
> install' hadoop-snappy. Which is (IMO) simpler than what will have to be done
> in once HBASE-3691 is committed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
