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
