Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 7 Apr 2014 21:12:16 +0000 (UTC)
From: "Mike Drob (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12678619.1384193060443.75762.1396905136367@arcas>
In-Reply-To: <JIRA.12678619.1384193060443@arcas>
References: <JIRA.12678619.1384193060443@arcas>
Subject: [jira] [Commented] (ACCUMULO-1879) Separate shell into its own
 module
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mike Drob commented on ACCUMULO-1879:
-------------------------------------

Accidentally mentioned ACCUMULO-1897 in the commit message :(

> Separate shell into its own module
> ----------------------------------
>
>                 Key: ACCUMULO-1879
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1879
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: shell
>            Reporter: Mike Drob
>            Assignee: Mike Drob
>             Fix For: 1.7.0
>
>
> It would be nice if the shell were its own module in the build for dependency management purposes. I'm not sure how many jars we are adding to core for the sake of the shell, but I know we at least have log4j and potentially others.
> Also, it would be nice if we could use just public APIs for the shell, and have it as an example of client code that can interact with accumulo.


--
This message was sent by Atlassian JIRA
(v6.2#6252)