[
https://issues.apache.org/jira/browse/CASSANDRA-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970871#action_12970871
]
Eric Evans commented on CASSANDRA-1848:
---------------------------------------
Tristan,
A couple of things, if we're putting Thrift and Avro classes (and MBeans, etc)
into their own jars, doesn't it make sense to omit those from the current jar
and set the jar's classpath accordingly?
Also, there are some classes in the o.a.c.thrift and o.a.c.avro packages that
are not client API. I'm not sure what the best way to handle this is; It might
make sense to move things around rather than deal with maintain
includes/excludes.
Finally, I didn't try to apply this patch, but if you haven't already done so,
make sure to do this against trunk. We're too late in the game to be making
changes like this in the 0.7 branch.
> 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
> Priority: Trivial
> Attachments: CASSANDRA-1848.patch
>
>
> 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.
