ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jonathan doklovic <jdoklo...@ibsys.com>
Subject Re: Install into shared if found in public?
Date Fri, 16 Nov 2007 18:24:54 GMT
Thanks,

I think a post-resolve-dependency trigger will do what I want.

- Jonathan

On Fri, 2007-11-16 at 08:37 +0100, Gilles Scokart wrote:
> You can maybe use a trigger on post-resolve-dependency [1].
> Alternatively, you if what you want achieve is avoiding to goe everytime to
> internet, you can also maybe use archiva [2].  There is still a bug when
> working with SNAPSHOT and latest.integration, but when using only static
> version it seems to work.
> 
> [1] http://ant.apache.org/ivy/history/trunk/configuration/triggers.html
> [2] http://maven.apache.org/archiva/
> 
> Gilles
> 
> 2007/11/15, jonathan doklovic <jdoklovic@ibsys.com>:
> >
> > Hi,
> >
> > I'm not sure if this is possible or recommended, but here's what I'd
> > like to do:
> >
> > setup an ivysettings file that's shared by my development team which
> > defines public repos and our shared enterprise repo.
> >
> > When the developer adds a dependency to the ivy.xml file for their
> > project and tries to run the compile task, I want to tell ivy to resolve
> > the dependencies using the shared repo first, if not found in there,
> > look in the public repo, and if found in the public repo, retrieve it,
> > publish it to the shared repo, and continue compiling.
> >
> > Does this make sense?
> >
> > Thanks,
> >
> > - Jonathan
> >
> >
> 
> 

Mime
View raw message