Return-Path: 
 <dev-return-87851-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
X-Original-To: apmail-ant-dev-archive@www.apache.org
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9009610DDD
	for <apmail-ant-dev-archive@www.apache.org>;
 Mon,  3 Mar 2014 13:59:28 +0000 (UTC)
Received: (qmail 47308 invoked by uid 500); 3 Mar 2014 13:59:27 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 46973 invoked by uid 500); 3 Mar 2014 13:59:26 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 46963 invoked by uid 99); 3 Mar 2014 13:59:25 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Mar 2014 13:59:25 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of baruchs@jfrog.com designates
 209.85.217.176 as permitted sender)
Received: from [209.85.217.176] (HELO mail-lb0-f176.google.com)
 (209.85.217.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Mar 2014 13:59:21 +0000
Received: by mail-lb0-f176.google.com with SMTP id 10so4646554lbg.35
        for <dev@ant.apache.org>; Mon, 03 Mar 2014 05:59:00 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc
         :content-type;
        bh=+aeB8UwfPAMU3o7Ti+pdfAKSgv0WMpDIlCOS0PxM97g=;
        b=DlcMpCir7TqCsXAcRszaPJOFwF1TAerJtKwUuGIoV+VffzVThogSv31/zqh8b83pAL
         Usa6DC2gIGBCq5EbzuoQZDKdwmPASQVTHUrno1wLRFrKDohOimG1mHC6OML0UhBJdFOv
         HYPAHOJwPtSTG4yD/2qM7q7JuEI5fqQOfTVKYjolKTrc5YuyCZ/eRpVEQrgRIo3Ujzaz
         tYnrF30JUAvG4JE8LOBIfkTh9vnTivS6Z57hMl1Tm39oY5CgQiPW4SL3C3XWmZNki6IQ
         zlAbl2oIUrnX7bPYqAbf6sMKWfYFSN3yDCBFuo40ps5Gqq09R9MNGWpuvNBqW3+n7sI0
         FNWg==
X-Gm-Message-State: 
 ALoCoQmg1SCCz5NGHfEVm4nz6biSbdR/Gx3D6oZWqW9LYPBjz1A8dueYUqlAG3diURoCX1nwYQeT
X-Received: by 10.152.30.68 with SMTP id q4mr3360997lah.44.1393855140268; Mon,
 03 Mar 2014 05:59:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.181.69 with HTTP; Mon, 3 Mar 2014 05:58:39 -0800 (PST)
From: JBaruch <jbaruch@jfrog.com>
Date: Mon, 3 Mar 2014 15:58:39 +0200
Message-ID: 
 <CAM-=Z3x196FM2sSfsG1xx0zZEPF4E8qtZV4q5wAj=NU90ybkig@mail.gmail.com>
Subject: Adding <jcenter> resolver
To: dev@ant.apache.org
Cc: Yoav Landman <yoavl@jfrog.com>, Dror Bereznitsky <drorb@jfrog.com>,
 Ophir Hordan <ophirh@jfrog.com>
Content-Type: multipart/alternative; boundary=089e0160b42c811a5f04f3b430e9
X-Virus-Checked: Checked by ClamAV on apache.org

--089e0160b42c811a5f04f3b430e9
Content-Type: text/plain; charset=UTF-8

Hi folks,

I'd like to contribute <jcenter> resolver to Ivy - similar to <ibiblio>,
but resolving from Bintray's JCenter instead of Maven Central.

JCenter is a superset of Maven Central and should ease the configuration
for obtaining artifacts which aren't present in ibiblio (as they will
probably be found in JCenter).

Groovy's Grape has JCenter as the first resolver in chain for that exact
reason.

The users will be given a simple way to add jcenter resolver (like they
have today in Gradle by adding jcenter() to repositories).

I believe it should be an easy task and will be glad to do it.

What do you think?


Baruch.

--
JFrog Developer Advocate
www.jfrog.com
+972544954353
@jbaruch <https://twitter.com/jbaruch/>
http://linkd.in/jbaruch

--089e0160b42c811a5f04f3b430e9--