[
https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741207#comment-13741207
]
stack commented on HBASE-9213:
------------------------------
[~roshan_naik] if we name it pom.xml.template, folks won't be able to do 'mvn
install', they will have to do 'mvn -f -pom.xml.template install'. That is
just going to piss off the majority of devs.
On your questions #2, I misread. No, there will not be a third artifact
published.... there will only be -hadoop1 and -hadoop2 artifacts (and the
-hadoop1, -hadoop2 comes after the version but be warned that the -test and
-src appendages that mvn adds are tacked on to the 'version' so come after the
-hadoop1, -hadoop2 suffix. See the published SNAPSHOTs for examples).
> 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
