AFAICS, the issue should be fixed now. If anybody is still seeing it,
please, let me know.
In fact, it used to be a couple of the OSGI tests that used the
CLIWrapper. OSGiManagementTest used to take care of the initialization
and cleaning up. It's removed now and the other utility class is using
the DMR API directly.
I'll continue looking into minimizing and removing the CLIWrapper in
favour of the CLI public API.
Alexey
On 04/28/2012 12:10 PM, Darran Lofthouse wrote:
For me this has been happening after a failed OSGI test that looks as
if
it may use the CLI as well so not sure if that is related.
Regards,
Darran Lofthouse.
On 04/28/2012 10:14 AM, Alexey Loubyansky wrote:
> It doesn't seem to be a CLI testsuite related issue.
> I simply removed all the CLI tests (cli local and the main testsuite),
> './build.sh clean' and './build.sh' and I still see it. Not after
every
> run though.
>
> Alexey
>
> On 04/27/2012 08:01 PM, Brian Stansberry wrote:
>> A number of people are reporting that after building the current
>> upstream master and running the testsuite, the terminal used to do that
>> no longer echos characters you type back to the screen.
>>
>> Just wanted to let you know we're aware of the issue and are working it,
>> with a pretty good idea as to the root cause.
>>
>> Some solutions people have used to get a normally functioning terminal
>> after this happens:
>>
>> 1) The Reset command from the Terminal menu.
>> 2) Running 'stty sane' from the command line
>> 3) Open a new terminal. ;)
>>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev