You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2017/06/01 18:02:04 UTC
[jira] [Commented] (IGNITE-4893) Release Ignite JDBC driver(s)
under a single JAR
[ https://issues.apache.org/jira/browse/IGNITE-4893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16033408#comment-16033408 ]
Denis Magda commented on IGNITE-4893:
-------------------------------------
[~vozerov], then it has to be clearly documented on the JDBC page.
> Release Ignite JDBC driver(s) under a single JAR
> ------------------------------------------------
>
> Key: IGNITE-4893
> URL: https://issues.apache.org/jira/browse/IGNITE-4893
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Denis Magda
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)