db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6719) Add derbyoptionaltools.jar to the class paths of the scripts in the bin directory
Date Fri, 19 Sep 2014 13:39:34 GMT

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

Kim Haase commented on DERBY-6719:

It looks as if this topic might need some updates to reflect this change in the scripts:


You could file a separate doc issue or just include the fix in this JIRA.

The Tools Guide itself recommends the use of derbyrun.jar instead of the scripts, so I don't
think any changes are needed there.

> Add derbyoptionaltools.jar to the class paths of the scripts in the bin directory
> ---------------------------------------------------------------------------------
>                 Key: DERBY-6719
>                 URL: https://issues.apache.org/jira/browse/DERBY-6719
>             Project: Derby
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions:,
>            Reporter: Rick Hillegas
>            Assignee: Myrna van Lunteren
>         Attachments: DERBY-6719.diff
> The derbyoptionaltools.jar should be added to the class paths constructed by all of the
scripts in the bin distros which include derby.jar. Otherwise, the Lucene plugin (and future
features which we put in derbyoptionaltools.jar) won't be available when you use the scripts
to run ij, the network server, and sysinfo.
> For instance, you will see information on this jar file if you run sysinfo this way...
> {noformat}
> java -jar derbyrun.jar sysinfo
> {noformat}
> …but not if you run the sysinfo script in the bin directory of a Derby installation.

This message was sent by Atlassian JIRA

View raw message