[
https://issues.apache.org/jira/browse/CASSANDRA-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090552#comment-13090552
]
Eric Evans commented on CASSANDRA-2761:
---------------------------------------
bq. One final thought: by coincidence, we broke the JDBC build again today with
CASSANDRA-3039. This isn't the first time this has happened. It's a minor win
but not negligible to catch those before commit because "ant test" runs both
suites.
Broke why? Because of Cassandra code that the driver depends on? That would
be an argument in favor of stabalizing the dependent code.
And, the inverse of this is that the drivers should ultimately be getting
tested against trunk, each active branch, and all past released versions
(limited of course to CQL availability). That is only going to be practical
through CI, and is made harder by your monolithic approach.
> 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
