[jboss-as7-dev] cli terminal changes
Tristan Tarrant
ttarrant at redhat.com
Mon May 7 10:46:31 EDT 2012
Good to know. As I'm developing a CLI for Infinispan, I want to make
sure I'm using something that will get fixed and updated properly. So if
AS7 + Forge standardize on jreadline, that's fine for me too :)
Tristan
On 05/07/2012 03:57 PM, "Ståle W. Pedersen" wrote:
> hi, to give you the history behind jreadline it started because i wanted
> vi-mode in jboss-cli. i started hacking on jline and asked the people
> behind it if they would be interested in the new features i wrote. the
> response was that they had stopped development of jline and would rather
> see me provide that for jline2.
> i started with jline2, but it took 2+ months for pull requests to be
> accepted and one night i thought i could make something better myself.
> so i did.
>
> to answer your question, jline2 do have issues with multiple line
> breaking, etc. i know forge is using it, but they have heavily modified
> it and has basically forked it into forge-core afaik.
> mike brock rewrote the input functionality for forge-jline2 which
> jreadline is also using.
> its been a while since i talked to lincoln regarding using jreadline,
> but we'll probably pick that up later if he thinks its useful.
>
> ståle
>
> On 05/07/2012 01:18 PM, Tristan Tarrant wrote:
>> On 05/07/2012 08:18 AM, Alexey Loubyansky wrote:
>>> I'd like to let everybody know that thanks to Stale's efforts we are
>>> switching from jline to Stale's jreadline project as the base
>>> console/terminal for the CLI.
>>>
>>> jline has a number of bugs that we can't do anything about. jreadline
>>> has fixed those and Stale is happy to continue improving things.
>> Was jline2 [1] considered ? JBoss Forge uses that.
>>
>> Tristan
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
More information about the jboss-as7-dev
mailing list