ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From wellgoonthen <>
Subject Re: External vs. Internal dependencies
Date Sun, 09 Sep 2012 18:24:29 GMT

Hi, thanks again for your help.

"If the ivy:resolve is taking so long, it sounds like you're not caching
dependencies when you should be."

All dependencies are cached and picked up from the local machine from my
local cache.  I know this for sure as I can run the build when not connected
to the network.

Is there any hints I could look at as to why resolving something that
already exists on disk may be so slow?


wellgoonthen wrote:
> Hi,
> I'm currently doing some build doctor work on our system build.  I've done
> quite a lot of work to implement a java incremental set up using uptodate
> etc.  This is great and saves a lot of time/work.  The biggest issue is
> now the ivy resolution.  To summarise we have two types dependencies that
> I call:
> - External - junit, log4j etc.
> - Internal - intra build module artifacts
> Now I can easily skip the resolution of the external artifacts by checking
> the "uptodateness" of the modules ivy.xml file to see if the version of
> junit has been changed, or a new 3rd party lib added to that module.  The
> issue I have is with the internal dependencies.
> For example if my build consists of modules A -> B -> C, built in that
> order.  I currently have to rely on ivy resolve to know if A's artifact
> has been rebuilt which would therefore trigger a rebuild of B.  
> To summarise I'm using ivy:resolve to do this and for one module that
> takes a total of 11 seconds, 8 seconds is spent resolving stuff.
> Does anyone have any ideas on this?
> Many thanks
> Richard Cole

View this message in context:
Sent from the ivy-user mailing list archive at

View raw message