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 < [email protected]> 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
