[
https://issues.apache.org/jira/browse/HBASE-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481850#comment-13481850
]
Roman Shaposhnik commented on HBASE-6929:
-----------------------------------------
@stack
if HBASE-4850 is not an option I believe you guys are on the right track. You
definitely don't want to use classifier for this so that leaves mucking with
the version string. As long as you come up with a reasonable encoding strategy
for pointing at various artifacts (e.g. hadoop2-secure, etc.) you can append
that to the version string. Watch out for things in the pom.xml that need to be
tweaked for each of these combinations -- I got bitten by default settings in
specially versioned pom files a couple of times.
> 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, hbase-6929_v2.patch
>
>
> 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
