-
Notifications
You must be signed in to change notification settings - Fork 545
Gradle 2.1 and duplicate entries #365
Comments
I saw this one too, and this is exactly what I was talking you about, @stephanenicolas I was trying to setup a toy project to submit this problem to @ducrohet and his team but, surprisingly, I'm not able to reproduce it with a brand new project. |
So it might be more project related then a general issue? More likely a gradle/gradle android plugin issue maybe, as this happened just after tools update. I have tried project cleaning using ./gradlew clean and building again to eliminate issues with build/ folder being filled with duplicate jars but it didn't help though. |
IHMO it's related to the Android Gradle Plugin or to Gradle itself. |
Guys, Please find out where the problem comes from and report an issue to android S.
|
Looks like support of mavens distributionManagement.relocate broken in gradle 2.1 http://central.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom
It may be fixed in robospice by switching from org.apache.commons:commons-io:1.3.2 to commons-io:commons-io:1.3.2 |
Can we have a fixed version in maven (e.g. 1.4.15)? Would be really useful for a lot of devs. Thank you for consideration. |
The workaround is really simple, you just need to replace RoboSpice's dependency with @maciejpigulski's code above:
If you have multiple |
Oh sorry, I though I already tried this, but now it works. Thank you for 2014-11-10 12:11 GMT+01:00 Nikola Keskinov notifications@github.com:
|
I followed @nkeskinov comments and added FIVE exclude's to all five of |
Hello everyone I have followed every comment but I can't still make my project to wok, this is my dependencies module in the main gradle: dependencies {
} any help would be appreciated. |
@alfco333 compile 'net.danlew:android.joda:2.7.2' I try it and work well |
Hello,
after updating to Gradle 2.1 and android gradle plugin to com.android.tools.build:gradle:0.13.1 I have encountered an issue while building my app that uses RoboSpice. This seems to be more like a proguard issue somehow but I cannot get it why it is happening:
This wasn't happening while using Gradle 1.x + com.android.tools.build:gradle:0.12.+. To fix this I have reviewed transient dependencies in the project, fixed all I could in terms of duplicate jars but problem still remained. I came up with a solution that looks like this:
That is, I have replaced commons-io dependency in robospice with a manual one. Now the project compiles without any erros.
What is also interesting is this part of output from ./gradlew dependencies:
And in particular this:
Does it mean that commons-io classes are indeed somehow referenced twice?
I am not a gradle power user so maybe I got it somehow wrong. Do you see any dangers in using self defined commons-io refrence?
Thanks.
The text was updated successfully, but these errors were encountered: