cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Tunnicliffe (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7491) Incorrect thrift-server dependency in 2.0 poms
Date Tue, 08 Jul 2014 19:35:05 GMT


Sam Tunnicliffe commented on CASSANDRA-7491:

Ok, leaving it as is just means that the poms deployed to mvn central are broken as the internal-only-0.3.3
jar won't be included as a transitive dependency, so you end up with a different set of libs
than if you checkout & build from source. That can be worked around of course, it's just
mildly annoying as it involves self-hosting the internal-only jar somewhere.

> Incorrect thrift-server dependency in 2.0 poms
> ----------------------------------------------
>                 Key: CASSANDRA-7491
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>            Reporter: Sam Tunnicliffe
>             Fix For: 2.0.10
> On the 2.0 branch we recently replaced thrift-server-0.3.3.jar with thrift-server-internal-only-0.3.3.jar
(commit says CASSANDRA-6545, but I don't think that's right), but didn't update the generated
pom that gets deployed to mvn central. The upshot is that the poms on maven central for 2.0.8
& 2.0.9 specify their dependencies incorrectly. So any project pulling in those versions
of cassandra-all as a dependency will incorrectly include the old jar.
> However, on 2.1 & trunk the internal-only jar was subsequently replaced by thrift-server-0.3.5.jar
(CASSANDRA-6285), which *is* available in mvn central. build.xml has also been updated correctly
on these branches.
> [~xedin], is there any reason for not switching 2.0 to thrift-server-0.3.5.jar ?

This message was sent by Atlassian JIRA

View raw message