You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by Alina Dima <di...@gmail.com> on 2009/06/09 16:18:39 UTC
ivy resolve for different configurations
Hi all,
I am just starting with Ivy on an already existing, relatively complicated,
build system and I am working on increasing the performance of the
resolve/retrieve Ivy operations. I would like to ask for your advice, what
do you think would be the main issues I should focus on regarding the
resolve/retrieve settings so that I make my resolve operation as fast as
possible?
A more specific question, I am not entirely sure how the Ivy resolve exactly
works, but if the very same module belongs to different configurations, will
it be resolved multiple times, once for each configuration? And if yes, is
there a workaround this?
Thanks
Alina
Re: ivy resolve for different configurations
Posted by Joshua Tharp <jo...@alumni.calpoly.edu>.
I've played with it a (very) little...
You need to declare a cache in your ivysettings.xml file. Then you can
specify how long items live in your cache before Ivy will go back out and
check again. You can set rules based on the organization or module so that
modules you develop get checked every time, and modules that are off the
Internet get checked daily.
Josh
On Mon, Jun 15, 2009 at 9:02 AM, Archie Cobbs <ar...@gmail.com>wrote:
> Gotcha. I don't know what that controls exactly. Presumably since we're
> talking about a cache then when the TTL expires the data in the cache is
> not
> used any longer, but I don't know details beyond that. If you do any simple
> experiments let us know.
>
> http://ant.apache.org/ivy/history/2.1.0-rc1/settings/caches/ttl.html
>
> -Archie
>
> On Mon, Jun 15, 2009 at 3:50 AM, Dima, Alina <
> alina.dima@immobilienscout24.de> wrote:
>
> > It is the ttl (Time To Live) attribute for the cache.
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Archie Cobbs [mailto:archie.cobbs@gmail.com]
> > Gesendet: Freitag, 12. Juni 2009 16:40
> > An: ivy-user@ant.apache.org
> > Betreff: Re: ivy resolve for different configurations
> >
> > On Wed, Jun 10, 2009 at 6:04 AM, Alina Dima <di...@gmail.com>
> wrote:
> >
> > > And yet another question: the TTL, how does the resolve handle this? I
> > was
> > > thinking to set a TTL for the external libraries, but, I am not sure
> how
> > > this would make the resolve faster? If the TTL is set, does it mean
> that
> > > for
> > > that time, Ivy resolve does not search anymore for the particular
> > > artifacts?
> > > Or is it only that it doesnt download them?
> > >
> >
> > Which actual ivy setting are you referring to by "TTL"? I'm a little
> fuzzy
> > in this area myself so I'm not sure what you mean.
> >
> > -Archie
> >
> > --
> > Archie L. Cobbs
> >
>
>
>
> --
> Archie L. Cobbs
>
Re: ivy resolve for different configurations
Posted by Archie Cobbs <ar...@gmail.com>.
Gotcha. I don't know what that controls exactly. Presumably since we're
talking about a cache then when the TTL expires the data in the cache is not
used any longer, but I don't know details beyond that. If you do any simple
experiments let us know.
http://ant.apache.org/ivy/history/2.1.0-rc1/settings/caches/ttl.html
-Archie
On Mon, Jun 15, 2009 at 3:50 AM, Dima, Alina <
alina.dima@immobilienscout24.de> wrote:
> It is the ttl (Time To Live) attribute for the cache.
>
> -----Ursprüngliche Nachricht-----
> Von: Archie Cobbs [mailto:archie.cobbs@gmail.com]
> Gesendet: Freitag, 12. Juni 2009 16:40
> An: ivy-user@ant.apache.org
> Betreff: Re: ivy resolve for different configurations
>
> On Wed, Jun 10, 2009 at 6:04 AM, Alina Dima <di...@gmail.com> wrote:
>
> > And yet another question: the TTL, how does the resolve handle this? I
> was
> > thinking to set a TTL for the external libraries, but, I am not sure how
> > this would make the resolve faster? If the TTL is set, does it mean that
> > for
> > that time, Ivy resolve does not search anymore for the particular
> > artifacts?
> > Or is it only that it doesnt download them?
> >
>
> Which actual ivy setting are you referring to by "TTL"? I'm a little fuzzy
> in this area myself so I'm not sure what you mean.
>
> -Archie
>
> --
> Archie L. Cobbs
>
--
Archie L. Cobbs
AW: ivy resolve for different configurations
Posted by "Dima, Alina" <al...@immobilienscout24.de>.
It is the ttl (Time To Live) attribute for the cache.
-----Ursprüngliche Nachricht-----
Von: Archie Cobbs [mailto:archie.cobbs@gmail.com]
Gesendet: Freitag, 12. Juni 2009 16:40
An: ivy-user@ant.apache.org
Betreff: Re: ivy resolve for different configurations
On Wed, Jun 10, 2009 at 6:04 AM, Alina Dima <di...@gmail.com> wrote:
> And yet another question: the TTL, how does the resolve handle this? I was
> thinking to set a TTL for the external libraries, but, I am not sure how
> this would make the resolve faster? If the TTL is set, does it mean that
> for
> that time, Ivy resolve does not search anymore for the particular
> artifacts?
> Or is it only that it doesnt download them?
>
Which actual ivy setting are you referring to by "TTL"? I'm a little fuzzy
in this area myself so I'm not sure what you mean.
-Archie
--
Archie L. Cobbs
Re: ivy resolve for different configurations
Posted by Archie Cobbs <ar...@gmail.com>.
On Wed, Jun 10, 2009 at 6:04 AM, Alina Dima <di...@gmail.com> wrote:
> And yet another question: the TTL, how does the resolve handle this? I was
> thinking to set a TTL for the external libraries, but, I am not sure how
> this would make the resolve faster? If the TTL is set, does it mean that
> for
> that time, Ivy resolve does not search anymore for the particular
> artifacts?
> Or is it only that it doesnt download them?
>
Which actual ivy setting are you referring to by "TTL"? I'm a little fuzzy
in this area myself so I'm not sure what you mean.
-Archie
--
Archie L. Cobbs
Re: ivy resolve for different configurations
Posted by Alina Dima <di...@gmail.com>.
Hi,
Thanks, I actually did mean artifacts.
And yet another question: the TTL, how does the resolve handle this? I was
thinking to set a TTL for the external libraries, but, I am not sure how
this would make the resolve faster? If the TTL is set, does it mean that for
that time, Ivy resolve does not search anymore for the particular artifacts?
Or is it only that it doesnt download them?
Thanks
Alina
On Tue, Jun 9, 2009 at 4:18 PM, Alina Dima <di...@gmail.com> wrote:
> Hi all,
>
> I am just starting with Ivy on an already existing, relatively complicated,
> build system and I am working on increasing the performance of the
> resolve/retrieve Ivy operations. I would like to ask for your advice, what
> do you think would be the main issues I should focus on regarding the
> resolve/retrieve settings so that I make my resolve operation as fast as
> possible?
>
> A more specific question, I am not entirely sure how the Ivy resolve
> exactly works, but if the very same module belongs to different
> configurations, will it be resolved multiple times, once for each
> configuration? And if yes, is there a workaround this?
>
> Thanks
> Alina
>
Re: ivy resolve for different configurations
Posted by Archie Cobbs <ar...@gmail.com>.
On Tue, Jun 9, 2009 at 9:18 AM, Alina Dima <di...@gmail.com> wrote:
> I am just starting with Ivy on an already existing, relatively complicated,
> build system and I am working on increasing the performance of the
> resolve/retrieve Ivy operations. I would like to ask for your advice, what
> do you think would be the main issues I should focus on regarding the
> resolve/retrieve settings so that I make my resolve operation as fast as
> possible?
>
There is a setting (can't remember it exactly) to tell ivy whether to
download ivy.xml files every time, or to use the previously cached one (if
the version has not changed). If you don't expect your ivy.xml files for the
same revision to change then this should help.
Also, using JAR files right out of the cache (e.g. for when building a
CLASSPATH) instead of copying them saves disk copies.
> A more specific question, I am not entirely sure how the Ivy resolve
> exactly
> works, but if the very same module belongs to different configurations,
> will
> it be resolved multiple times, once for each configuration? And if yes, is
> there a workaround this?
Modules contain configurations, not the other way around.
If by "module" you meant "artifact" then the answer is no, the artifact will
only be included once even if it is listed in multiple configurations.
-Archie
--
Archie L. Cobbs