You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/06/01 11:09:04 UTC

[jira] [Resolved] (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:all-tabpanel ]

Vladimir Ozerov resolved IGNITE-4893.
-------------------------------------
    Resolution: Won't Fix

It is ok to ship new JDBC driver as a part of {{ignite-core}}.

> 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
>             Fix For: 2.1
>
>
> 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)