On Sep 7, 2009, at 6:12 PM, Peter Ledbrook wrote:
Hi,
First, a quick note to let you know that Grails has borrowed the
Gradle dependency DSL:
http://github.com/grails/grails/commit/b1a9a83a4bc530e7d0b2dd24215404b56a0cd0f9
Take a look at the new BuildConfig.groovy file in that commit to see
the DSL in action.
Cool.
Eventually Gradle will become modular enough to be used as embedded to
support such stuff. But we are not there yet.
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.
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.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
