Hi Jaco,
On Jun 7, 2008, at 8:02 PM, jaco.uys wrote:
Hi,
Ok, after some more playing around it seems that the issue is with the
amount of resolvers.
I have the following resolvers configured:
addFlatDirResolver('lib', new File(rootDir, 'lib2'))
addMavenRepo()
classpathResolvers.add(name: 'jboss',
url:'http://repository.jboss.org/maven2')
classpathResolvers.add(name: 'java.net',
url:'http://download.java.net/maven/2')
classpathResolvers.add(name: 'jibx',
url:'http://jibx.sf.net/maven2')
As more resolvers are added, so the performance of finding a jar in
the
local lib decreases quite dramatically. I guess there is some check
that is
done against all resolvers regardless.
BTW: If you start Gradle with -j, the debug output of Ivy is printed
to the console.
- Hans
Regards Jaco
--
View this message in context: http://www.nabble.com/performance-of-
addFlatDirResolver-tp17709833p17711478.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
