Thanks for the response Hans.
>> Second, I have a couple of questions, one related to the DSL, and one
>> related to Ivy. Starting with the DSL, I notice in BuildConfig.groovy
>> that the last argument to the main "compile" dependency list is a map
>> containing "transitive: false". Is this part of the Gradle dependency
>> DSL? If so, is it supposed to block transitive dependencies?
>
> Yes. You can either block transitive dependencies for single dependencies or
> for configurations. For example we block transitive dependencies for the
> compile configuration, to motivate people to be explicit about what are
> there first level dependencies.
It appears that Graeme hadn't implemented it yet, but it's there now.
>> The more important Ivy-related question is this: is there any way to
>> get the Ivy resolution time down to less than a second? We're using a
>> flat-file resolver, but it's still taking > 3s to resolve the default
>> dependencies. That just seems wrong.
>
> I guess it always depend on how many dependencies your are dealing with. But
> looking at BuildConfig.groovy, 3 seconds looks like a lot. When we have Ivy
> performance issues, I often try the equivalent ant build to see how it
> performs and go from there.
Graeme has improved the performance by disabling Ivy validation and
the output report(s). It's down to 1.5s now. We'll probably continue
to look at ways to eliminate the calls to Ivy, for example by only
resolving dependencies when BuildConfig.groovy changes.
Peter
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
