[
https://issues.apache.org/jira/browse/CASSANDRA-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090494#comment-13090494
]
Jonathan Ellis commented on CASSANDRA-2761:
-------------------------------------------
bq. There was a Jira yes
I couldn't find one, and the svn commit messages didn't mention it. I still
can't find one.
bq. So all I need to do is find a ticket and a +1 and I can -1 this, and revert
your revert?
The point of making a ticket with a patch (or a shell script if you're throwing
svn refactoring around -- you can do mv's from a working copy, not just on the
repository, btw) is that people can review it and see if the result matches
what they thought they were going to get out of it. In this case it's clear
that it didn't, and we ended up with making things worse in exchange for a
promise to clean it up eventually.
(Of course, even with proper review, sometimes we've needed to revert things
after unexpected problems arose. But skipping the review makes that more
likely.)
It's been *over two months.* So let's reboot, and do it right. Note that this
time around I got everything in one commit (well, one for trunk, and one for
drivers) so "reverting the revert" will be easy.
> 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
