[
https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741099#comment-13741099
]
Roshan Naik commented on HBASE-9213:
------------------------------------
Stack,Elliott,
Could you confirm ... henceforth, building hbase by running mvn on the
default pom.xml would be incorrect ? once must run mvn against the pom
generated by the gen script (from HBSE-8224). If thats true perhaps it would be
good idea to rename the pom.xml to say pom.xml.template. That way people are
not likely to build hbase the wrong way accidentally.
Stack,
I am confused that you answered 'yes' to my question #2. My asked if a third
artifact by name of hbase-common-0.96 will be published in addition to
hbase-common-0.96-hadoop1 & hbase-common-0.96-hadoop2. if the answer is really
'yes', it is unclear to me what is the purpose of it and how it differs from
the other two.
> 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
