improve dependency situation between JDBC driver and Cassandra
--------------------------------------------------------------
Key: CASSANDRA-2936
URL: https://issues.apache.org/jira/browse/CASSANDRA-2936
Project: Cassandra
Issue Type: Improvement
Components: API, Core
Affects Versions: 0.8.1
Reporter: Eric Evans
Priority: Minor
The JDBC jar currently depends on the {{apache-cassandra-$version}} jar,
despite the fact that it only (directly) uses a handful of Cassandra's classes.
In a perfect world, we'd break those classes out into their own jar which both
the JDBC driver and Cassandra (ala {{apache-cassandra-$version.jar}}) could
depend on. However, the classes used directly don't fall out to anything that
makes much sense organizationally (short of creating a
{{apache-cassandra-misc-$version.jar}}), and the situation only gets worse when
you take into account all of the transitive dependencies.
See CASSANDRA-2761 for more background, in particular
([this|https://issues.apache.org/jira/browse/CASSANDRA-2761?focusedCommentId=13048734&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13048734]
and
[this|https://issues.apache.org/jira/browse/CASSANDRA-2761?focusedCommentId=13050884&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13050884])
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
