Hi
One of the reasons I wanted to move away from maven (and hopefully to
gradle) was that I have a rather large java multiproject, with lots of
dependency jars, and keeping everything up to the same level was a
pain without transitive dependencies. But from what I can tell from
the userguide and my testing, gradle does not do transitive dependency
between projects. Is this true?
For example, if I have projects A, B, C, D, etc with each depending on
the previous like B/build.gradle having:
dependencies {
compile project(':A') { transitive = true }
}
and C/build.gradle having
dependencies {
compile project(':B') { transitive = true }
}
Then if a class in C uses classes in A, it appears that I have to
explicitly list A in the build.gradle of C?
Is there a way say project C depends not only project B, but also all
of project B's dependencies in its compile configuration? I thought
that the "transtive = true" did this, but it appears not.
I can understand that there may be arguments for explicitly listing
the jars and versions and not relying on transitive dependence, but in
a multiproject I think there would be advantages to only listing
information once instead of repeating it in each subproject.
thanks,
Philip
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
