cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2761) JDBC driver does not build
Date Wed, 24 Aug 2011 22:08:29 GMT


Eric Evans commented on CASSANDRA-2761:

I don't understand. What version will "come with their [server]?"

Wherever we publish the source, be it an SVN checkout with an SVN revision ID, a date-based
development snapshot, or a full-on release artifact, if there is driver source contained within
then people are going to be encouraged to think of those drivers as being the same version
as the node (e.g. 0.8.9).  They're also going to be encouraged to think that those drivers
are the best choice to use with the corresponding node.  It's futile to think they won't,
and having other vectors (www.a.o, PyPI, etc), will only add to the confusion. 

Consider postgresql: the server is distributed on, and psycopg is distributed
over PyPI. Nobody gets confused about staying on an obsolete version of psycopg.

That's the model I see us moving towards. (As you know, we recently got the Python cql driver
on PyPI.)

You make an excellent point.  Pyscopg is maintained in a completely different repository (git://
than Postgesql (git:// and is released (and published)
separately, (which is in fact consistent with best practice elsewhere).

> JDBC driver does not build
> --------------------------
>                 Key: CASSANDRA-2761
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.0
>            Reporter: Jonathan Ellis
>            Assignee: Rick Shaw
>             Fix For: 1.0
>         Attachments: jdbc-driver-build-v1.txt, v1-0001-CASSANDRA-2761-cleanup-nits.txt
> Need a way to build (and run tests for) the Java driver.
> Also: still some vestigal references to drivers/ in trunk build.xml.
> Should we remove drivers/ from the 0.8 branch as well?

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message