[
https://issues.apache.org/jira/browse/BIGTOP-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14123565#comment-14123565
]
Andrew Purtell commented on BIGTOP-1427:
----------------------------------------
bq. Look for yourself in the dev-support script.
I'm aware of this procedure as I run through it every time I make an HBase 0.98
release.
bq. But if there any changes to make - they would have to be make in the
upstream including re-thinking of the versioning of the hbase artifacts.
We have two binary-incompatible releases due to compiling against different
major versions of Hadoop, and the POM munging is the only viable workaround of
limitations of Maven classifiers that we have found. But if you have a better
concrete solution, by all means present it on dev@hbase.
bq. BTW, we can't change the version of HBase in the bom file, because the
version of the release source artifact is 0.98.2
Ah, yeah, that's annoying.
> HBase build should build hbase-***-hadoop2 by default
> -----------------------------------------------------
>
> Key: BIGTOP-1427
> URL: https://issues.apache.org/jira/browse/BIGTOP-1427
> Project: Bigtop
> Issue Type: Bug
> Components: build
> Affects Versions: 0.7.0
> Reporter: stanley shi
>
> Flume is depending on hbase-**-hadoop2, but the hbase build is not providing
> this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
