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 AE35210648 for ; Sat, 10 Aug 2013 21:37:49 +0000 (UTC) Received: (qmail 1503 invoked by uid 500); 10 Aug 2013 21:37:49 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 1482 invoked by uid 500); 10 Aug 2013 21:37:49 -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 1447 invoked by uid 99); 10 Aug 2013 21:37:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Aug 2013 21:37:49 +0000 Date: Sat, 10 Aug 2013 21:37:49 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CASSANDRA-2987) maven-ant-tasks should have more than one repo defined 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-2987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis resolved CASSANDRA-2987. --------------------------------------- Resolution: Won't Fix Given that we've survived without this for two years, I'm guessing it's not worth the trouble. > maven-ant-tasks should have more than one repo defined > ------------------------------------------------------ > > Key: CASSANDRA-2987 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2987 > Project: Cassandra > Issue Type: Improvement > Reporter: Brandon Williams > Assignee: Stephen Connolly > Priority: Trivial > > If, for whatever reason, repo2.maven.org is down or unreachable, you can no longer build cassandra (unless you already have all the deps). -- 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