Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7637E1771E for ; Fri, 3 Apr 2015 14:37:53 +0000 (UTC) Received: (qmail 19705 invoked by uid 500); 3 Apr 2015 14:37:53 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 19666 invoked by uid 500); 3 Apr 2015 14:37:53 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 19655 invoked by uid 99); 3 Apr 2015 14:37:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2015 14:37:53 +0000 Date: Fri, 3 Apr 2015 14:37:53 +0000 (UTC) From: "Sam Tunnicliffe (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CASSANDRA-7491) Incorrect thrift-server dependency in 2.0 poms MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-7491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe resolved CASSANDRA-7491. ---------------------------------------- Resolution: Fixed Reproduced In: 2.0.9, 2.0.8 (was: 2.0.8, 2.0.9) CASSANDRA-7594 brought the generated pom.xml back in line with the jar in lib/ > Incorrect thrift-server dependency in 2.0 poms > ---------------------------------------------- > > Key: CASSANDRA-7491 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7491 > Project: Cassandra > Issue Type: Bug > Components: Packaging > Reporter: Sam Tunnicliffe > Fix For: 2.0.15 > > > 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 (v6.3.4#6332)