On 9/02/10 5:27 AM, Felix Gnass wrote:
Hello,
I noticed a change in the behavior from Gradle 0.8 to 0.9 when it
comes to the resolution of runtime dependencies. I've attached a
ZIP-file containing a simple example.
The test-case consists of two projects called "project" and
"framework". The latter one is a multi-project build with dependencies
between its modules:
framework/libA/build.gradle
dependencies {
compile project(':libB')
}
framework/libB/build.gradle
dependencies {
runtime project(':libC')
}
The other project has a module-dependency to libA:
project/build.gradle
dependencies {
compile 'eg.example:libA:1.0.0-SNAPSHOT'
}
With Gradle 0.8 everthing works as expected and running `gradle war`
in ./project creates a WAR-file containing all three JARs (libA, libB
and libC).
With Gradle 0.9-20100208163629+0100, only libA and libB are present,
whereas libC is missing.
Is this the intended behavior or did I encounter a bug?
This looks like a bug to me. Could you add a JIRA issue for it?
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
