[
https://issues.apache.org/jira/browse/CASSANDRA-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050534#comment-13050534
]
Eric Evans commented on CASSANDRA-2761:
---------------------------------------
{quote}
I can try an get them all in but I think we should seriously rethink that
strategy for now. With this many dependancies they should probably be put in
their own jar(s). It would really make the driver jar have to keep up with
detailed dependency changes in the server code base. Miss one and it's messy
and the errors are non-obvious.
{quote}
What would you call such a jar? When I looked at this, there didn't seem to be
any delineation that made sense.
{quote}
I was a big whiner about not carrying around the whole server just for client
access, but until it is re-factored, I can now appreciate the horror that will
commence if we piece-meal drag over classes from the server into the JAR.
{quote}
What are these 50 other class dependencies? Where are they being drug in?
> 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
>
>
> 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
