[
https://issues.apache.org/jira/browse/CASSANDRA-5833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725447#comment-13725447
]
Alex Tang commented on CASSANDRA-5833:
--------------------------------------
Yes, the fact that cassandra-thrift imports cassandra-thrift means that you
can't get away from this problem. Disabling the duplicate-finder extension is a
sub-optimal way to fix the problem as having the exact same class in two
separate jar files can lead to very odd bugs later in life if the files ever
diverge.
> Duplicate classes in Cassandra-all package.
> -------------------------------------------
>
> Key: CASSANDRA-5833
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5833
> Project: Cassandra
> Issue Type: Bug
> Components: API, Packaging
> Affects Versions: 1.1.6, 1.2.7
> Reporter: sam schumer
> Labels: maven
>
> As of Cassandra-All version 1.1.6 the classes
> org.apache.cassandra.thrift.ITransportFactory and
> org.apache.cassandra.thrift.TFramedTransportFactory are located in both the
> cassandra-thrift and the cassandra-all Maven JARS, and caasandra-thrift is
> imported by cassandra-all POM. This makes the cassandra-all package
> unbuildable when using the duplicate-finder Maven extension. The files were
> originally copied over due to
> [CASSANDRA-4668|https://issues.apache.org/jira/browse/CASSANDRA-4668]. All
> versions since have failed to build when using this maven extension.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
