hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-3873) Mavenize Hadoop Snappy JAR/SOs project dependencies
Date Tue, 10 May 2011 16:31:47 GMT
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

(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

View raw message