[
https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13743162#comment-13743162
]
stack commented on HBASE-9213:
------------------------------
[~sershe] You mean that when builds run as they do up on apache build box, that
the produce is hbase-0.97.0-SNAPSHOT and not hbase-0.97.0-SNAPSHOT-hadoop1? If
so, yeah. Profiles don't work. Can't set version from profile. Can't even
set version from command line. I suppose I could amend the apache and ec2
builds to use our little script so we produce hadoop1 or hadoop2 builds but I
don't think that is what you want.
I just noticed that our hbase-common depends on hadoop so yeah, different
dependencies dependent on if for hadoop1 or hadoop2...
> create a unified shim for hadoop 1 and 2 so that there's one build of HBase
> ---------------------------------------------------------------------------
>
> Key: HBASE-9213
> URL: https://issues.apache.org/jira/browse/HBASE-9213
> Project: HBase
> Issue Type: Brainstorming
> Components: build
> Reporter: Sergey Shelukhin
> Fix For: 0.96.0
>
>
> This is a brainstorming JIRA. Working with HBase dependency at this point
> seems to be rather painful from what I hear from other folks. We could do the
> hive model with unified shim, built in such manner that it can work with
> either version, where at build time dependencies for all 2-3 versions are
> pulled and the appropriate one is used for tests, and when running HBase you
> have to point at Hadoop directory to get the dependencies. I am not very
> proficient at maven so not quite certain of the best solution yet.
--
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
