[
https://issues.apache.org/jira/browse/CASSANDRA-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970898#action_12970898
]
Stephen Connolly commented on CASSANDRA-1848:
---------------------------------------------
Eric,
How about changing the build to produce the following jars:
cassandra-all-___.jar (the current jar)
cassandra-thrift-___.jar (the thrift client)
cassandra-avro-___.jar (the avro client)
cassandra-hadoop-___.jar (the hadoop support classes)
cassandra-server-jar (the remainder of cassandra-all after removing the above
three)
Could we get that in the 0.7.0 time frame (so I can get the maven publishing of
at least the thrift and avro client jars in the 0.7.0 timeframe)
The hadoop stuff uses the cloudera version of hadoop which is not availble in
repo1.maven.org which is why I'd prefer to split that out.
I am less concerned with the thrift & avro jars containing more than they
should, as the key here is to trim the dependencies down to those that are
available in central... as cassandra is modifying avro, and avro is an apache
project, it is no big deal to publish the cassandra avro special build under
the org.apache.cassandra gId, the same goes for libthrift.
It would be nice to have the server end of things (excluding the hadoop stuff)
as a separate jar to enable fancy things like a maven-cassandra-plugin that I
have a rough version of ready to contrib... it enables integration testing in a
much easier fashion for projects building with maven.... of course I need to
know what artifacts are being generated before I can contrib it.
> 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, CASSANDRA-1848_with_hadoop.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.
