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 "Richard N. Hillegas (Jira)" <ji...@apache.org> on 2020/03/08 23:12:00 UTC

[jira] [Updated] (DERBY-7071) Getting started documentation needs to add derbytools to the client classpath

     [ https://issues.apache.org/jira/browse/DERBY-7071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard N. Hillegas updated DERBY-7071:
---------------------------------------
    Attachment: derby-7071-01-aa-addToolsJarToClientClasspath.diff

> Getting started documentation needs to add derbytools to the client classpath
> -----------------------------------------------------------------------------
>
>                 Key: DERBY-7071
>                 URL: https://issues.apache.org/jira/browse/DERBY-7071
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.15.1.3, 10.15.2.0
>            Reporter: Richard N. Hillegas
>            Assignee: Richard N. Hillegas
>            Priority: Major
>         Attachments: derby-7071-01-aa-addToolsJarToClientClasspath.diff
>
>
> The client driver now lives in derbytools.jar. Our documentation needs to say that the client-side classpath needs derbytools.jar. See for instance http://db.apache.org/derby/docs/10.15/getstart/twwdactivity4.html It is likely that other examples need to be updated.
> This issue was raised in the following derby-user email thread: http://apache-database.10148.n7.nabble.com/I-don-t-find-the-JDBC-driver-class-in-derbyclient-jar-td151132.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)