db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-1447) add command line history to ij
Date Thu, 16 Aug 2012 05:11:38 GMT

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

Kristian Waagan commented on DERBY-1447:

Found this old thread by coincidence: https://groups.google.com/forum/?fromgroups#!topic/jvm-languages/0uxWJdR79Xs[1-25]

Haven't looked into this, but I was wondering if instead of bundling JLine with Derby we could
make ij use it automatically if it's on the classpath. However, I think this will still require
some environment setup, which makes the manual wrapper solution just as viable. Maybe it can
be seen as a security issue too?

> add command line history to ij
> ------------------------------
>                 Key: DERBY-1447
>                 URL: https://issues.apache.org/jira/browse/DERBY-1447
>             Project: Derby
>          Issue Type: Improvement
>          Components: Tools
>            Reporter: Gary Orser
>            Priority: Minor
>              Labels: ij
>         Attachments: DERBY-1447-1a.patch, jline-0_9_5.jar, jline.diff
> Using the command line tool 
> org.apache.derby.tools.ij
> is user unfriendly.

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


View raw message