You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Eric Evans (JIRA)" <ji...@apache.org> on 2011/06/01 00:44:47 UTC

[jira] [Commented] (CASSANDRA-2263) cql driver jar

    [ https://issues.apache.org/jira/browse/CASSANDRA-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041882#comment-13041882 ] 

Eric Evans commented on CASSANDRA-2263:
---------------------------------------

Gah, I'd fixed this locally but forgot to commit.  It's there now.

> cql driver jar
> --------------
>
>                 Key: CASSANDRA-2263
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2263
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 0.8 beta 1
>            Reporter: Eric Evans
>            Assignee: Eric Evans
>            Priority: Minor
>              Labels: cql
>             Fix For: 1.0
>
>         Attachments: v1-0001-CASSANDRA-2263-don-t-ship-jdbc-in-main-jar.txt
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Work was done in CASSANDRA-1848  to create a jar for the CQL Java driver.  The generated Thrfit code was broken out into it's own jar as well, since that is a dependency for both servers and clients. However, based on the work currently happening in CASSANDRA-2262 and CASSANDRA-2124, it seems that additional dependencies will exist, and new jar(s) will need to be created.
> The easiest way to fix this will probably be to put copies of all of {{o.a.c.db.marshal}} and {{o.a.c.utils}}, and a copy of {{o.a.c.config.ConfigurationException}} into the CQL driver jar (a split along those lines to create another jar doesn't make sense IMO).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira