[
https://issues.apache.org/jira/browse/DERBY-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005329#comment-17005329
]
Richard N. Hillegas commented on DERBY-7063:
--------------------------------------------
As part of the modularization work, the JDBC drivers moved into derbytools.jar.
The release notes do not make this clear. Please include derbyclient.jar,
derbyshared.jar, and derbytools.jar on your client-side classpath.
> Cannot connect using squirrel 3.3.0
> -----------------------------------
>
> Key: DERBY-7063
> URL: https://issues.apache.org/jira/browse/DERBY-7063
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Server
> Affects Versions: 10.15.1.3
> Reporter: sagar
> Priority: Major
>
> The derbyclient.jar file does not have the
> org.apache.derby.jdbc.ClientDriver.class
>
> When I add the jar file in squirrel, ssquirrel automatically detects the
> driver but since this class is missing it does not detect it.
> Till now I was using 10.11.1.1 database. Now I have decided to upgrade and
> this issue cropped up.
>
> Yes Derby has switched to the module system from 10.15.1.3 but the derby
> documentation mentions connection to Network Server similar to previous as
> using the
> org.apache.derby.jdbc.ClientDriver and this class is missing from the new
> derbyclient.jar.
>
>
> Squirrel is running on Java 1.8
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
