hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8224) Add '-hadoop1' or '-hadoop2' to our version string
Date Wed, 31 Jul 2013 19:35:52 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725633#comment-13725633

stack commented on HBASE-8224:

The profile activation mess is biting us.  We will always pull in hadoop1 default in a downstream
project even when built w/ custom hadoop2 pom.xml which hard codes our compatibility module
at hadoop2, etc., because resultant module poms have two profiles and no profile means default

Trying to hack about in downstream projects w/ excludes is awful; we shouldn't have downstreamers
have to do this (could exlude hadoop1 everywhere and do explicit include of hadoop2 but it
is awfully arcane).

We cannot expect downstreamers specify a profile building: e.g. downstream projects 'work'
if we add -Dhadoop.profile=2.0 but that is again asking too much of downstreamers; they should
just select the hbase jars they want and we should transitively include (caveat maven transitive
include mechanism, especially regards test-jars is random seemingly).

Given maven poms do not support xinclude and given that pom element duplication is rife already,
I think I have to script -hadoop1 and -hadoop2 build/publication (unless anyone has better
> Add '-hadoop1' or '-hadoop2' to our 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.95.2
>         Attachments: 8224-adding.classifiers.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

View raw message