[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-8224:
-------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks for the reviews lads and for trying out the product. mvn release
struggle is still an issue and I'll update the refguide as I run 0.95.2 so it
is informed by an actual release.
As to doing same for 0.94, I commented over on the 0.94-specific issue. It
should be easier there to do same thing since not modularized.
On packaging for bigtop, this should help. Lets open new issue for any
specifics needed.
> Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to
> version string
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-8224
> URL: https://issues.apache.org/jira/browse/HBASE-8224
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 0.98.0, 0.95.2
>
> Attachments: 8224-adding.classifiers.txt, 8224.gen.script.txt,
> 8224.gen.scriptv3.txt, 8224.gen.scriptv3.txt, 8224v5.txt,
> hbase-8224-proto1.patch
>
>
> So we can publish both the hadoop1 and the hadoop2 jars to a maven
> repository, and so we can publish two packages, one for hadoop1 and one for
> hadoop2, given how maven works, our only alternative (to the best of my
> knowledge and after consulting others) is by amending the version string to
> include hadoop1 or hadoop2.
--
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
