Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 20 Aug 2015 00:50:46 +0000 (UTC)
From: "Nick Dimiduk (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12857116.1439963051000.113636.1440031846366@Atlassian.JIRA>
In-Reply-To: <JIRA.12857116.1439963051000@Atlassian.JIRA>
References: <JIRA.12857116.1439963051000@Atlassian.JIRA>
 <JIRA.12857116.1439963051009@arcas>
Subject: [jira] [Commented] (HBASE-14250) branch-1.1 hbase-server test-jar
 has incorrect LICENSE
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nick Dimiduk commented on HBASE-14250:
--------------------------------------

Wires crossing. I now understand you to mean the subject of this ticket.

When I make RC, it's from my mac. I'm working from a pristine, case sensitive image created for the rc. git clone, followed by checkout origin/branch-1.1, and then ./dev-support/make_rc.sh.

I've just built from my usual dev sandbox with {{mvn clean install -DskipTests -Dcheckstyle.skip -Dmaven.javadoc.skip -Prelease}}, effectively the [first command|https://github.com/apache/hbase/blob/branch-1.1/dev-support/make_rc.sh#L57] from make_rc. The LICENSE in hbase-server/target/hbase-server-1.1.2-tests.jar looks like the regular apache 2 license. I see no mention of orca logo or jquery.

> branch-1.1 hbase-server test-jar has incorrect LICENSE
> ------------------------------------------------------
>
>                 Key: HBASE-14250
>                 URL: https://issues.apache.org/jira/browse/HBASE-14250
>             Project: HBase
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.1.2
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Blocker
>
> test-jar LICENSE file for hbase-server claims jquery and the orca logo are present in the jar, when they are not.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)