Adam Murdoch <adam@...> writes:
> No. It should resolve conflicts, regardless of where the
> dependencies come from. Do you have some particular examples?
yes, here is my dependencies declaration:
dependencies {
compile fileTree(dir: 'libs', includes: ['*.jar'])
compile 'com.github.droidfu:droid-fu:1.0-SNAPSHOT'
compile 'oauth.signpost:signpost-core:1.2.1.2'
compile 'oauth.signpost:signpost-commonshttp4:1.2.1.2'
}
now in libs/ there is a commons-codec-1.4.jar, and Signpost has a
transitive dependency to commons-codec-1.3. Here is what the
runtime configuration set of files looks like
(configurations.runtime.files, paths shortened):
./libs/apache-mime4j-0.6.jar
./libs/commons-codec-1.4.jar
./libs/httpmime-4.0.1.jar
.gradle/cache/.../droid-fu-1.0-SNAPSHOT.jar
.gradle/cache/.../signpost-core-1.2.1.2.jar
.gradle/cache/.../commons-codec-1.3.jar
.gradle/cache/.../signpost-commonshttp4-1.2.1.2.jar
.gradle/cache/.../httpcore-4.0.1.jar
.gradle/cache/.../httpclient-4.0.1.jar
.gradle/cache/.../commons-logging-1.1.1.jar
note how commons-codec appears twice in there.
Shouldn't just the 1.4 JAR be retained?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
