[
https://issues.apache.org/jira/browse/CASSANDRA-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000546#comment-13000546
]
T Jake Luciani commented on CASSANDRA-1848:
-------------------------------------------
Looks like a sane approach....
Would it be possible to put o.a.c.thrift and o.a.c.cql under their respective
jars too?
> Separate thrift and avro classes from cassandra's jar
> -----------------------------------------------------
>
> Key: CASSANDRA-1848
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1848
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Affects Versions: 0.7.0 rc 2
> Reporter: Tristan Tarrant
> Assignee: Eric Evans
> Priority: Trivial
> Fix For: 0.8
>
> Attachments: CASSANDRA-1848.patch, CASSANDRA-1848_with_hadoop.patch,
> v1-0001-CASSANDRA-1848-compile-bytecode-to-build-classes-main.txt,
> v1-0002-compile-thrift-generated-classes-to-separate-jar.txt,
> v1-0003-compile-CQL-driver-to-separate-jar.txt
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Most client applications written in Java include the full
> apache-cassandra-x.y.z.jar in their classpath. I propose to separate the avro
> and thrift classes into separate jars.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
