cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Connolly (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-1848) Separate thrift and avro classes from cassandra's jar
Date Fri, 07 Jan 2011 16:04:46 GMT


Stephen Connolly commented on CASSANDRA-1848:

I don't cate about the tools being split out.... just thought it would make using them from
e.g. mvnsh easier.... (i.e. they are executable jars with the correct dependencies, so you
could just run the jar direct from the central repository, the classpath would be set up for
you and the executable jar would start the tool)

But hey, I don't care much about splitting them out.... 

ACTUALLY, scratch that it could be trivially handled by just having an empty jar with the
dependencies and the main class defined.

> Separate thrift and avro classes from cassandra's jar
> -----------------------------------------------------
>                 Key: CASSANDRA-1848
>                 URL:
>             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.

View raw message