[
https://issues.apache.org/jira/browse/HBASE-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13475762#comment-13475762
]
stack edited comment on HBASE-6929 at 10/14/12 4:16 AM:
--------------------------------------------------------
Maven makes no sense (I know no one will read and register the statement I just
made because all have same opinion).
-Dclassifier just doesn't work on mvn command line. Maybe hadoop pom needs an
amendment so all is just optional or some such voodoo but if you specify
-Dclassifier and try to deploy, it doesn't matter what combination seemingly
(at least going by my hours spent trying to figure mvn vagaries), it just tries
to include dependencies w/ the classifier attached...e.g.
randomjar-yourclassifier.jar, and so on. This fails.
The attached patch modifies the hadooop 2.0 profile so the hbase jar built has
an hadoop2 suffix (also ups the version of our apache pom from 8 to 11). It
does not decorate the test, source or javadoc jars w/ the classifier suffix.
I went ahead and uploaded 0.94.3-SNAPSHOTs to maven repository, w/ the hadoop2
classification:
https://repository.apache.org/content/repositories/snapshots/org/apache/hbase/hbase/0.94.3-SNAPSHOT/.
Is this all that is needed? If so I'll commit this patch as is (I think
you'd depend on the hbase-0.94.3-SNAPSHOT but would reference explicitly
hbase-0.94.3-SNAPSHOT-hadoop2.jar if an hadoop2 dependency).
was (Author: stack):
Maven makes no sense (I know no one will read and register the statement I
just made).
-Dclassifier just doesn't work. Maybe hadoop pom needs an amendment so all is
just optional or some such voodoo but if you specify -Dclassifier and try to
deploy, it doesn't matter what combination seemingly (at least going by my
hours spent trying to figure mvn vagaries), it just tries to include
dependencies w/ the classifier attached...
The attached patch modifies the hadooop 2.0 profile so the jar built has an
hadoop2 suffix. Is this enough. It does not decorate the test, source or
javadoc jars. Is that OK? I went ahead and added 0.94.3-SNAPSHOTs w/ the
hadoop2 classification. Is this enough? If so I'll commit this patch as is
(I think you'd depend on the hbase-0.94.3-SNAPSHOT but would explicitly
reference explicitly hbase-0.94.3-SNAPSHOT-hadoop2.jar if an hadoop2 dependency.
I've pushed an hadoop2 SNAPSHOT. See here:
https://repository.apache.org/content/repositories/snapshots/org/apache/hbase/hbase/0.94.3-SNAPSHOT/
Let us know if this works, or if more is needed.
> 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
