Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
Presently, if someone uses the client node based driver (with Spring XML config) from an SQL tool we demand to add to the classpath all the jars from "libs" and "ignite-spring", "ignite-indexing" subdirectories (up to 15! jars in total).
As for the thin client based driver, the things are easier but the driver is in "ignite-core.jar".
It would be more user-friendly if the JDBC drivers are packaged under single “ignite-jdbc.jar” and located in special directory of a release bundle. All the dependencies have to be in this jar.
Attachments
Issue Links
- Is contained by
-
IGNITE-4922 JDBC Driver: renew thin client based solution
- Resolved