accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1879) Separate shell into its own module
Date Fri, 15 Nov 2013 02:21:24 GMT

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

Christopher Tubbs commented on ACCUMULO-1879:
---------------------------------------------

log4j is probably not strictly necessary as a dependency. The shell doesn't have the same
API compatibility concerns as the rest of the code, so if there is something using a log4j
object, we can probably change it easily.

But... it still might be useful to have the shell in its own module and packaging. I think
that would have to depend on whether we can finally sever the tie with HdfsZooInstance or
not, using client config files to locate the instance.

> 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
>             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.1#6144)

Mime
View raw message