Open siyamed opened 9 years ago
yeah it would be nice to update this, since it causes lot's of dependency conflicts.
My dependencies looks like this because of it
compile('com.octo.android.robospice:robospice:1.4.14') {
exclude group: 'org.apache.commons', module: 'commons-io'
}
compile('com.octo.android.robospice:robospice-retrofit:1.4.14') {
exclude group: 'org.apache.commons', module: 'commons-io'
}
compile('com.octo.android.robospice:robospice-okhttp:1.4.14') {
exclude group: 'org.apache.commons', module: 'commons-io'
}
The reason is that commons introduced some feature, by memory an array copy, that was not available on android in some SDK release.
If you could try to upgrade the version and get the build to pass or identify the SDK minimum version, we can talk about upgrading it.
Note that nothing prevents you from using a more recent commons version in your own app..
If Robospice does not use the new feature, why is it a problem to upgrade? I see String.getBytes() was added in API 9. http://developer.android.com/reference/java/lang/String.html#getBytes%28java.nio.charset.Charset%29. Perhaps that is the source of this problem - http://stackoverflow.com/questions/17359163/apache-commons-io-on-android
Is there any specific reason to keep commons io dependency at 1.3.2 ? Current version is 2.4
http://commons.apache.org/proper/commons-io/upgradeto2_4.html
Thanks