Fix (some) problems with libraries in the ADT 17 Plugin
Hey guys!
This will be a quick post. Did you update the ADT plugin to v17? Did you find that there are problems with libraries?
The solution (for some of those problems) is:
- If your jar libraries are in a lib folder, rename it to libs.
- Remove all your jar libraries from the Build Path of your project. Don’t need to add them again to the Build Path.
- In your libs folder, you should have just the jar libraries that your project is using. You can’t have different versions of a single library. This is because if you’ve noticed, Eclipse creates now a reference in the Build Path called “Android Dependecies” and he puts there all the jar files that are in your libs folder.
- Follow steps 1, 2 and 3 for each Android Library Project that your project is using.
- Make a project clean.
Hope it helps anybody!
I found some help here: http://android.foxykeep.com/dev/how-to-fix-the-classdefnotfounderror-with-adt-17
UPDATE: You can find official ¡nfo on Android Dependecies at this link: http://tools.android.com/recent/dealingwithdependenciesinandroidprojects


Great Article!
I’m quite sick of those Google upgrades with structural changes and no instructions on how adapt your projects.
Yes. this is a good post.
Note that there was a lot of info posted here: http://tools.android.com/recent/dealingwithdependenciesinandroidprojects
This was linked from the blogpost and the release notes.
Thanks @Xavier! I updated the post with that link.
Sure next time we (developers) will read the release notes more carefully
Why waste precious minutes reading documentation when you can invest hours on trying by yourself? XD XD
Thanks for the comment!
This doesn’t seem to apply to jar files that are in Java-only projects.
The only way I can get those to work is by manually editing the Android project’s .classpath file with exported=”true”
I wasn’t able to try that, but thanks for the tip!!
Google is always creating a problem without any prior information
Automatic inclusion in Android Dependencies is nice. But it seems it doesn’t work with test project.
All my testing ant scripts are ruined. I don’t know for how long will I have to manually test all updates before I or someone find solutions for buildxml someday…
Tio en serio, no puc compilar i m’estic desesperant, ja he perdut 3 o 4 hores provan coses diferents…
Una de dos, o em dona error de Dalvik, o la activitat no se m’executa per què em dona error de mapView dins del Fragment…
ho he provat tot, totes les combinacions, he seguit mil tutorials diferents i res…
si vols agregam al gtalk i em faries un favor si parlessim del tema, perquè això dels mapes per mi es molt urgent xD
cesaryomismo@gmail.com !!
You’re a life saver. I’ve been struggling with this problem for a week.