Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 7 Aug 2013 14:52:49 +0000 (UTC)
From: "Jonathan Hsieh (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12639872.1364586537466.16560.1375887169777@arcas>
In-Reply-To: <JIRA.12639872.1364586537466@arcas>
References: <JIRA.12639872.1364586537466@arcas>
Subject: [jira] [Commented] (HBASE-8224) Publish hbase build against h1 and
 h2 adding '-hadoop1' or '-hadoop2' to version string
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Hsieh commented on HBASE-8224:
---------------------------------------

Hey [~saint.ack@gmail.com], the svn commit seems to be missing the dev-support scripts.  Can you or someone who tested it commit the correct version?
                
> 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