Gradle currently always ignores the cache for file:// based repositories when
using the ivy {} repository notation. Your best bet is to stick with
FileSystemResolver for the time being.
Please raise a problem on our forums <http://forums.gradle.org> so we can
discuss what to do about smarter behaviour with slow file based repositories.
On 25/11/2011, at 3:11 PM, kulbhushan wrote:
> Dependency caching works when using the old FileSystemResolver on both
> milestone-5 and milestone-6.
>
> On Fri, Nov 25, 2011 at 8:29 PM, Luke Daley-2 [via Gradle] <[hidden email]>
> wrote:
>
> On 25/11/2011, at 1:16 PM, kulbhushan wrote:
>
> > Ever since we have upgraded to using gradle 1.0 milestone 5, the build
> > times
> > have slowed down. The build that earlier took 1 minute is now taking about
> > 10 minutes. On investigating this issue, I found that all the dependencies
> > are being picked up from the central repository and they are never cached
> > in
> > the gradle cache.
> >
> > When upgrading to milestone-5, a change was made in the way the repository
> > is defined. Now, the repository is defined as follows:
> >
> > repositories {
> > ivy {
> > artifactPattern
> > "<network-location>/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"
> >
> > ivyPattern
> > "<network-location>/[organisation]/[module]/ivy-[revision].xml"
> > }
> > }
> >
> > Before upgrade the repositories were defined using FileSystemResolver and
> > everything worked fine at that time. The repository was defined as follows
> > before upgrade:
> >
> > repositories {
> > add(new org.apache.ivy.plugins.resolver.FileSystemResolver()) {
> > name = 'synygy-resolver'
> > addIvyPattern
> > "<network-location>/[organisation]/[module]/ivy-[revision].xml"
> > addArtifactPattern
> > "<network-location>/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"
> >
> > }
> > }
> >
> > Please let me know what is preventing the dependencies from being cached.
> What happens if you use the same code (i.e. FileSystemResolver) with m6?
>
> --
> Luke Daley
> Principal Engineer, Gradleware
> http://gradleware.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
>
> If you reply to this email, your message will be added to the discussion
> below:
> http://gradle.1045684.n5.nabble.com/Dependencies-are-not-being-cached-since-upgrading-to-milestone-5-tp5022756p5022959.html
> To unsubscribe from Dependencies are not being cached since upgrading to
> milestone-5, click here.
> NAML
>
>
> View this message in context: Re: Dependencies are not being cached since
> upgrading to milestone-5
> Sent from the gradle-user mailing list archive at Nabble.com.
--
Luke Daley
Principal Engineer, Gradleware
http://gradleware.com
