[jira] [Commented] (ACCUMULO-4441) ConsoleReader created in Main breaks any external jars use of Console.readLine

["Michael Miller (JIRA)" <ji...@apache.org>]

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

Michael Miller commented on ACCUMULO-4441:
------------------------------------------

[~jvines@gmail.com] I believe this was fixed in https://github.com/apache/accumulo/commit/612ede6960503a8ffef0d30bd73503015c52274d
This was a fix to a similar problem with ACCUMULO-4374

> ConsoleReader created in Main breaks any external jars use of Console.readLine
> ------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4441
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4441
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.7.2
>            Reporter: John Vines
>
> ACCUMULO-3514 introduced an autoloader for starting up our various functions as well as external utilities that are using our provided classpath. 
> Unfortunately with this work, the shell was more or less left alone. This means in teh Shell's empty constructor, which is now constructed no matter what, creates a ConsoleReader. And sadly, an unclosed ConsoleReader laying around breaks System.console().readLine by restricting it to reading just one character.
> Ideally the Shell's empty constructor, like all of the other autowired services, should be empty and not creating an impact on the entire VM.



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