Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: domain of miguel.griffa@gmail.com
 designates 209.85.218.226 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=qwrJdP1bU0eN+0AvR+dYSxRM3vcSpoI3BOA99/OH0/aon3XOGIKabt6pA9BB9Gw2ii
         S90M26+iin3uHJJCJek/Llu9kQCzAl3qVpkgvXEhMEXLdl209T07XdkNJ1v+JnlJ9psZ
         yOl/zzlTtNvioSQUhFPoraVg4fC5znIPXlWRs=
MIME-Version: 1.0
In-Reply-To: <000701ca320d$76926630$63b73290$@de>
References: <000701ca320d$76926630$63b73290$@de>
Date: Thu, 10 Sep 2009 09:21:13 -0300
Message-ID: <e8fb92d10909100521wea3562ch5f4b51359c557474@mail.gmail.com>
Subject: Re: Is there a real(!) advantage of Ivy over placing the depends in
	the VCS
From: Miguel Griffa <miguel.griffa@gmail.com>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=0015174c37404da4200473383ca7

--0015174c37404da4200473383ca7
Content-Type: text/plain; charset=ISO-8859-1

Hi,
Personally I addressed this issue by creating  acustom repository (a simple
dir actually). It is also usefull to migrate jars from VCS, since when I
migrate a project, I copy jars from project to our repo. If jars are
available on the net, better, but I get sure with this setup. Ivy lets you
configure patterns in sucha a way that you only need on dir with jars.
Hope this helps

Miguel

On Thu, Sep 10, 2009 at 8:54 AM, Sebastian Krysmanski <
sebastian@krysmanski.de> wrote:

> Hello,
>
> recently someone recommended Ivy to me because he saw that we were hosting
> our project dependencies in our Subversion repository. I took this
> opportunity to have a look at Ivy and on first glance Ivy seemed very nice.
> However I see a major disadvantage over dependencies in a VCS repository:
> If
> a project is dormant for a longer period of time an artifact (i.e. a
> library) may longer be available (in a certain, required version or the
> repository may not exist anymore).
>
> If we were using Ivy this would result in the project no longer being able
> to be built. If we're placing the libraries in our SVN repository however,
> the project could still be built. How does Ivy "address" this drawback? Is
> there any commonly used solution to solve this problem?
>
> Regards
> Sebastian
>
>


-- 
---
Miguel Griffa

--0015174c37404da4200473383ca7--