[
https://issues.apache.org/jira/browse/CASSANDRA-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978751#action_12978751
]
Stephen Connolly commented on CASSANDRA-1848:
---------------------------------------------
To be clear, what dependencies between these artifacts are you expecting?
I expect to see something like
cassandra-thrift -> libthrift
cassandra-cql -> (none)?
cassandra-jmx -> (none)?
cassandra-hadoop -> hadoop jars and perhaps cassandra-thrift / cassandra-cql
cassandra-tools... I would prefer to see something like
cassandra-tools-core -> cassandra-jmx, etc
cassandra-tools-cli -> cassandra-tools-core [make this an executable jar]
cassandra-tools-nodetool -> cassandra-tools-core [make this an executable jar]
cassandra-tools-clustertool -> cassandra-tools-core [make this an executable
jar]
then
cassandra-server instead of cassandra-main [make this an executable jar]
But hey' what do I know
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
