hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6929) Publish Hbase 0.94 artifacts build against hadoop-2.0
Date Mon, 15 Oct 2012 05:17:03 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475978#comment-13475978

stack commented on HBASE-6929:

I can add hadoop2 to the name of the target artifact but not to the test jar.  When maven-jar-plugin
makes the jar, it uses a hard-coded 'tests' classifier.  I cannot override it w/o changing
plugin code (adding a classifier to maven-jar-plugin is just ignored).

I tried various other things.  I tried getting build-helper-maven-plugin to attach the test
jar at package time but only seemed to end up doubling the test jars installed (a variant
of this suggestion http://stackoverflow.com/questions/8499266/maven-deploy-source-classifiers).
 They still didn't have the right name on install.  I think the maven-jar-plugin attaches
the test jar before I can intercede later w/ the build-helper-maven-plugin.

I tried setting the finalName to hadoop2 when we are using the hadoop2 profile.  This gets
pretty far.  See below:

[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ hbase ---
[INFO] Installing /Users/stack/checkouts/0.94/target/hbase-0.94.3-SNAPSHOT-hadoop2.jar to
[INFO] Installing /Users/stack/checkouts/0.94/pom.xml to /Users/stack/.m2/repository/org/apache/hbase/hbase/0.94.3-SNAPSHOT/hbase-0.94.3-SNAPSHOT.pom
[INFO] Installing /Users/stack/checkouts/0.94/target/hbase-0.94.3-SNAPSHOT-hadoop2-tests.jar
to /Users/stack/.m2/repository/org/apache/hbase/hbase/0.94.3-SNAPSHOT/hbase-0.94.3-SNAPSHOT-tests.jar
[INFO] Installing /Users/stack/checkouts/0.94/target/hbase-0.94.3-SNAPSHOT-hadoop2-sources.jar
to /Users/stack/.m2/repository/org/apache/hbase/hbase/0.94.3-SNAPSHOT/hbase-0.94.3-SNAPSHOT-sources.jar

I cannot get install though to write the local repo w/ the names I told it to use.  Looking
at the install plugin, it uses maven itself copying artifacts (The above logging is the output
of a repository 'event' as artifacts are copied in).  I cannot put config on the install plugin
to have it use my final name rather than the one it composes from base pom attributes.

Anyone else have a suggestion?

Is the test jar really needed?  The hadoop1 built one doesn't work w/ hadoop2?
> Publish Hbase 0.94 artifacts build against hadoop-2.0
> -----------------------------------------------------
>                 Key: HBASE-6929
>                 URL: https://issues.apache.org/jira/browse/HBASE-6929
>             Project: HBase
>          Issue Type: Task
>          Components: build
>    Affects Versions: 0.94.2
>            Reporter: Enis Soztutar
>         Attachments: 6929.txt
> Downstream projects (flume, hive, pig, etc) depends on hbase, but since the hbase binaries
build with hadoop-2.0 are not pushed to maven, they cannot depend on them. AFAIK, hadoop 1
and 2 are not binary compatible, so we should also push hbase jars build with hadoop2.0 profile
into maven, possibly with version string like 0.94.2-hadoop2.0. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message