You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Andreas Pieber (JIRA)" <ji...@apache.org> on 2011/03/17 08:24:29 UTC

[jira] Created: (KARAF-520) JLine wired autocompletion behaviour when starting in linux via java process

JLine wired autocompletion behaviour when starting in linux via java process
----------------------------------------------------------------------------

                 Key: KARAF-520
                 URL: https://issues.apache.org/jira/browse/KARAF-520
             Project: Karaf
          Issue Type: Bug
          Components: console
    Affects Versions: 2.2.0, 3.0.0
         Environment: Linux via Java Process
            Reporter: Andreas Pieber


When you try to start Karaf via a separate Java Process in Linux (as shown here e.g. https://github.com/openengsb/openengsb-maven-plugin/blob/master/src/main/java/org/openengsb/openengsbplugin/Provision.java) the autocompletion on console creates wired completion problems. Text is duplicated, back does not work as expected, ... While the "real" text always is correct the otuput does not reflect this in any way.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (KARAF-520) JLine wired autocompletion behaviour when starting in linux via java process

Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated KARAF-520:
---------------------------------------

    Fix Version/s: 3.1.0

> JLine wired autocompletion behaviour when starting in linux via java process
> ----------------------------------------------------------------------------
>
>                 Key: KARAF-520
>                 URL: https://issues.apache.org/jira/browse/KARAF-520
>             Project: Karaf
>          Issue Type: Bug
>          Components: console
>    Affects Versions: 2.2.0, 3.0.0
>         Environment: Linux via Java Process
>            Reporter: Andreas Pieber
>             Fix For: 3.1.0
>
>
> When you try to start Karaf via a separate Java Process in Linux (as shown here e.g. https://github.com/openengsb/openengsb-maven-plugin/blob/master/src/main/java/org/openengsb/openengsbplugin/Provision.java) the autocompletion on console creates wired completion problems. Text is duplicated, back does not work as expected, ... While the "real" text always is correct the otuput does not reflect this in any way.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (KARAF-520) JLine wired autocompletion behaviour when starting in linux via java process

Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Pieber updated KARAF-520:
---------------------------------

    Fix Version/s: 3.0.1
    
> JLine wired autocompletion behaviour when starting in linux via java process
> ----------------------------------------------------------------------------
>
>                 Key: KARAF-520
>                 URL: https://issues.apache.org/jira/browse/KARAF-520
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-shell
>    Affects Versions: 2.2.0, 3.0.0
>         Environment: Linux via Java Process
>            Reporter: Andreas Pieber
>             Fix For: 3.0.1, 3.1.0
>
>
> When you try to start Karaf via a separate Java Process in Linux (as shown here e.g. https://github.com/openengsb/openengsb-maven-plugin/blob/master/src/main/java/org/openengsb/openengsbplugin/Provision.java) the autocompletion on console creates wired completion problems. Text is duplicated, back does not work as expected, ... While the "real" text always is correct the otuput does not reflect this in any way.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira