On 1/26/07, Robert Buck <[EMAIL PROTECTED]> wrote:
> -----Original Message----- > From: Gilles Scokart [mailto:[EMAIL PROTECTED] > Sent: Friday, January 26, 2007 10:35 AM > To: [email protected] > Subject: RE: machine local repositories and disconnected development > > > > > -----Original Message----- > > From: Robert Buck [mailto:[EMAIL PROTECTED] > > > > Question: What out of the box IVY tooling allows a copy of > an artifact > > to be duplicated into the "shared" repository? > > > > I guess you can use the install task. Without having to hard code that logic in multiple places (once for the dependency and once for the install) is there some way to automatically trigger on any download from the public repository to duplicate the download in the next tier of repositories (named or automatic). I'd like to avoid the otherwise redundant information - the dependency information and the install task information.
I'm not sure to understand correctly what you want, but if what you want is some sort of proxy, then the short answer is that there's no such mechanism in Ivy for the moment. Glen some time ago talked about some kind of proxy he developed that was useful for the use with Ivy or Maven. You can also use a standard proxy, or check what Maven Archiva can offer. On the pure Ivy perspective, triggering an install during the resolve process is quite easy (using triggers for instance), but this should be done with a strong care of concurrency, which is not easy. That's why I think this should better be done in a server side solution (like a proxy). Xavier
