If you are using Maven you need to use deploy:deploy-file to upload the new support library jar into your local Maven repository. Make sure you specify the same groupId and artifactId as the existing support library and only update the version.
The usage of deploy:deploy-file is easily Google-able since I'm on mobile and can't paste the full command.
Yes. This works from command line but not in Idea and I think that it is bug in Idea. It compile apk lib separately and only with dependencies defined in Sherlock pom. I will enter bug for it.
If it has a different groupId and/or artifactId you should add an <exclude> entry to the ABS dependency and add an explicit dependency on the new version. Something like this:<dependency><groupId>com.actionbarsherlock</groupId><artifactId>actionbarsherlock</artifactId><version>4.2.0</version><excludes><exclude><groupId>com.google.android</groupId><artifactId>support-v4</artifactId></exclude></excludes></dependency><dependency><groupId>whatever</groupId><artiactId>support-library</artifactId><version>r11</version>
</dependency>
On Monday, November 19, 2012 1:27:29 AM UTC-8, Tomáš Procházka wrote:
This is problem if want to use support library imported to the own repo by https://github.com/mosabua/maven-android-sdk-deployerIt has different groupId :-(I hope that official support from Google will be soon :-(
--