Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <10833426.52251289596096037.JavaMail.jira@thor>
Date: Fri, 12 Nov 2010 16:08:16 -0500 (EST)
From: "Konstantin Boudnik (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-7014) Generalize CLITest structure and
 interfaces to faciliate upstream adoption (e.g. for web testing)
In-Reply-To: <14414782.154171288411940612.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931527#action_12931527 ] 

Konstantin Boudnik commented on HADOOP-7014:
--------------------------------------------

Perhaps I have misunderstood your suggestion, but there's already Shell class in common. 
I agree though  that prefix "i" isn't something inherently Java... sounds more like C# word ;(

> Generalize CLITest structure and interfaces to faciliate upstream adoption (e.g. for web testing)
> -------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7014
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7014
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 0.22.0
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>         Attachments: HADOOP-7014.patch, HADOOP-7014.patch, HADOOP-7014.patch
>
>
> There's at least one use case where TestCLI infrastructure is helpful for testing projects outside of core Hadoop (e.g. Owl web testing). In order to make this acceptance easier for upstream project TestCLI needs to be refactored.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.