Hi Andrew,
On Thu, Mar 25, 2010 at 9:09 AM, Andrew Schetinin <[email protected]>wrote:
> Hi Hans,
>
> The search finds nothing.
> grep SNAPSHOT `find ./ -name build.gradle`
>
> for 3rd party dependencies I'm using fixed revisions only, but there are
> dependencies between the modules (it is a multi-project build), and I'm not
> sure about them.
>
> Actually, I tried testing now a single module which only depends on
> 3rdparty libraries, and there are no any unnecessary lookups - the build
> time is the same with and without that command line option.
>
> But when I'm running a complete build without that option, I'm definitely
> having the problem of long lookups.
>
> This probably means that my internal dependencies between the modules are
> configured incorrectly - they should only do local lookups, without checking
> the online repositories.
>
> The following is how I configure the dependencies - the first line is for
> internal modules, and the second line is for 3rdparty modules.
>
> compile project(':tms.proto'), project(':tms.engine:core')
> compile 'commons-lang:commons-lang:2.4'
>
> And the following is repositories configuration in the master/build.gradle
> file:
>
> repositories {
> //flatDir( id: 'local-repo', name: 'Local Repo', dirs:
> file('../repos'))
> logger.info "Before configuring repositories"
> // "checkmodified: false" did not work yet, unfortunately (or at
> least it seems so)
> mavenCentral( checkmodified: false )
> mavenRepo( id: 'guice', name: 'Guice Repo', urls: ['
> http://guice-maven.googlecode.com/svn/trunk'<http://guice-maven.googlecode.com/svn/trunk%27>],
> checkmodified: false )
> mavenRepo( id: 'codehaus-release', name: 'Codehaus Release Repo',
> urls: ['http://repository.codehaus.org'], checkmodified: false )
> mavenRepo( id: 'EclipseLink Repo', name: 'EclipseLink Repo', urls:
> ['
> http://www.eclipse.org/downloads/download.php?r=1&nf=1&file=/rt/eclipselink/maven.repo'<http://www.eclipse.org/downloads/download.php?r=1&nf=1&file=/rt/eclipselink/maven.repo%27>],
> checkmodified: false )
> logger.info "After configuring repositories"
> }
>
> May be what I should do is to somehow attach each artifact to its
> repository?
>
We will enable that in 1.0.
> That would save Ivy from searching in all repositories...
>
But if you don't use dynamic revisions, ivy shouldn't use the repos at all.
I'm wondering if any of the transitive dependencies are snapshots?
If you like, you could attach the -d output of a build where the long
checking is taking place (or send it to me as a private mail if you don't
want to expose some stuff too much).
- Hans
--
Hans Dockter
Founder, Gradle
http://www.gradle.org, http://twitter.com/gradleorg
CEO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
>
> Regards,
>
> Andrew
>
>
> On Thu, Mar 25, 2010 at 9:38 AM, Geronimo M. H. <[email protected]>wrote:
>
>> Am Thursday 25 March 2010 08:28:14 schrieb Hans Dockter:
>> > On Thu, Mar 25, 2010 at 8:07 AM, Andrew Schetinin
>> <[email protected]>wrote:
>> > > Hi Hans,
>> > >
>> > > I'm not sure what the "dynamic revisions" are... could you provide a
>> link
>> > > with an explanation?
>> > Stuff like:
>> >
>> > dependencies {
>> > compile "junit:junit:4.+", "somegroup:someorg"1.0-SNAPSHOT"
>> > }
>>
>> I use dynamic revisions for my own stuff and fixed revisions for external
>> libraries, so the last timings was with dynamic revisions.
>>
>> kind regards
>>
>> Geronimo
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>
>
> --
> --
> Andrew Schetinin
>
