You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2014/09/23 22:19:34 UTC
[jira] [Resolved] (DERBY-6719) Add derbyoptionaltools.jar to the
class paths of the scripts in the bin directory
[ https://issues.apache.org/jira/browse/DERBY-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-6719.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.12.0.0
10.11.1.2
The doc and code changes have gone in, and have been backported to 10.11.
The doc changes are visible in the latest alpha docs. Resolving.
> 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: 10.11.1.1, 10.12.0.0
> Reporter: Rick Hillegas
> Assignee: Myrna van Lunteren
> Labels: derby_backport_reject_10_10
> Fix For: 10.11.1.2, 10.12.0.0
>
> Attachments: DERBY-6719.diff, DERBY-6719_doc.diff, tgs26250.html
>
>
> 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
(v6.3.4#6332)