karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Moquin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-2303) Command completer stopped working after RC1
Date Mon, 20 May 2013 13:01:18 GMT

    [ https://issues.apache.org/jira/browse/KARAF-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661961#comment-13661961

Ryan Moquin commented on KARAF-2303:

I can only think it's my jdk which is 1.7.0_17-b02.   Hotspot client is
build 23.7-b01 (if that second part even matters).  If I can ssh locally to
it amd ot works fine I can only think it's the jdk.  Since every single
other machine I try it on works.. it seems very localized to my
environment.  Just weird rc1 is fine.

On May 20, 2013 8:19 AM, "Jean-Baptiste Onofré (JIRA)" <jira@apache.org>

> Command completer stopped working after RC1
> -------------------------------------------
>                 Key: KARAF-2303
>                 URL: https://issues.apache.org/jira/browse/KARAF-2303
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-shell
>    Affects Versions: 3.0.0
>         Environment: Windows 7, JDK 7
>            Reporter: Ryan Moquin
> At some point after Karaf 3.0.0RC1, pressing the tab key at the terminal has stopped
showing a list of commands or completing a command.  It just tabs the cursor in the console.
 Something I noticed that is related, is that if I hit ctrl-c while I'm tailing a log in the
Karaf Console, it normally would return me to the Karaf prompt.  It now terminates Karaf all
together now.  Ctrl-D doesn't terminate Karaf either.  I guess as I'm writing this and thinking
of more things to test, something seems to just plain be broken in the Karaf shell all together.
> Just to reiterate, running RC1 works perfectly fine.  When I'm testing on the latest
snapshot, I'm just unzipping and running, to make sure it's clear I'm not making any modifications

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message