Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E497710E21 for ; Fri, 7 Feb 2014 00:46:24 +0000 (UTC) Received: (qmail 30941 invoked by uid 500); 7 Feb 2014 00:46:20 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 30841 invoked by uid 500); 7 Feb 2014 00:46:19 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 30815 invoked by uid 99); 7 Feb 2014 00:46:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Feb 2014 00:46:19 +0000 Date: Fri, 7 Feb 2014 00:46:19 +0000 (UTC) From: "Aleksandr Shulman (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-10481) API Compatibility JDiff script does not properly handle arguments in reverse order MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Aleksandr Shulman created HBASE-10481: ----------------------------------------- Summary: API Compatibility JDiff script does not properly handle arguments in reverse order Key: HBASE-10481 URL: https://issues.apache.org/jira/browse/HBASE-10481 Project: HBase Issue Type: Bug Components: test Affects Versions: 0.96.1.1, 0.94.16, 0.98.0, 0.99.0 Reporter: Aleksandr Shulman Assignee: Aleksandr Shulman Priority: Minor Fix For: 0.98.0, 0.99.0, 0.96.1.1, 0.94.16 [~jmhsieh] found an issue when doing a diff between a pre-0.96 branch and a post-0.96 branch. Typically, if the pre-0.96 branch is specified first, and the post-0.96 branch second, the exisitng logic handles it. When it is in the reverse order, that logic is not handled properly. The fix should address this. -- This message was sent by Atlassian JIRA (v6.1.5#6160)