commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Libbrecht (JIRA)" <>
Subject [jira] Resolved: (JELLY-175) patch for jelly-tags-interaction
Date Wed, 10 May 2006 08:03:09 GMT
     [ ]
Paul Libbrecht resolved JELLY-175:

    Resolution: Fixed

This in the current version about to be released (I think).

> patch for jelly-tags-interaction
> --------------------------------
>          Key: JELLY-175
>          URL:
>      Project: Jelly
>         Type: Improvement

>   Components: taglib.interaction
>     Versions: 1.0
>  Environment: I've tested this in windows with and without cygwin.
>     Reporter: Ryan Christanson
>     Assignee: Paul Libbrecht
>     Priority: Minor
>      Fix For: 1.1
>  Attachments: interaction.patch, patch.txt
> I've attached a patch to the commons-jelly-tags-interaction jar. This
> patch makes it so the interaction task will try to use jline:
> Jline makes it so a java console will have tab completion, and
> history, and other goodies.
> This is great, because the maven-console plugin uses the
> commons-jelly-tags-interaction jar. So if you update the
> commons-jelly-tags-interaction jar, and then tell the maven console
> plugin to use the new jar, then your maven console will have history,
> and tab completion.
> I've set it up to remember all of the commands typed in any console,
> further it uses that history as the tab completion source - so you can
> tab complete past commands.
> I've tested this in windows and it works great, but in windows with
> cygwin, it doesn't do the fancy completion, but still works.
> By the way, in windows, jline's lib doesn't support arrows for
> history, so use CONTROL+P and CONTROL+N.
> Its possible that there might be a better way to integrate jline into
> this lib, i've just done what looked like the quickest way to get it
> working so my maven console would have history and tab completion.
> Maybe this feature could be enabled with a tag attribute?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message