[
https://issues.apache.org/jira/browse/CASSANDRA-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090383#comment-13090383
]
Jonathan Ellis commented on CASSANDRA-2761:
-------------------------------------------
bq. I also realize that there is more work needed here to decouple the JDBC
driver and make this all work better, work that I've volunteered to do. I
haven't had as much time to spend on this lately, but that should be changing
RSN.
It's been another two weeks and we're still in this no-man's land where git
can't see drivers, the jdbc build is a big TODO, and anything that depends on
jdbc like 3010 is basically SOL.
Again, I'm not against purity, but it's clear that the original breaking out of
drivers/ was done prematurely (was there even a Jira ticket with a patch? It
looks like we went from "that's a good idea" on -dev to ripping apart svn).
I've reverted things until the breakout can be done properly.
> JDBC driver does not build
> --------------------------
>
> Key: CASSANDRA-2761
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2761
> 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: http://www.atlassian.com/software/jira
