Android upgrade ADT to 22 third party jar package caused by ClassNotFoundException and Noclassdeffounderror exception resolution

Encountered an error while using the Android-universal-image-loader jar package for the asynchronous loading framework:

java.lang.NoClassDefFoundError:com.nostra13.universalimageloader.core.imageloaderconfiguration$ Builder later discovered through careful study that this is not related to the framework, this is due to

Your ADT upgrade to 22 out of the question, ADT22 more reasonable than ADT21. After the adt17 version, import the third-party jar package, to establish a libs directory, cannot use the Lib name, ADT will automatically rely on the jar, do not manually add

Add it.

Reference Link: http://blog.csdn.net/huzgd/article/details/7604069

Note: If you have add yourself, you can configure the build path to delete the package you imported

Analyze the difference between ADT22 and ADT21:

ADT21 Chart:

ADT22 Chart:

Steps to resolve:

1. First of all, deal with the above questions

2.adt22 needs to tick Android Private libraries and Android Dependencies, so developers can decide for themselves which packages to export to the APK. For example, the program is for a high-version Android system, you can choose not to

Export some support packages for the lower version (e.g. V4, v7, etc.)

3.libs inside the jar package also should note, because after ADT17 is automatic import, so do not put the system some packages to this directory, you can see the console (console) is said to have the same package, if any, delete

4. Compile (Project--clean)

Description: There may be some steps you do not need, and I may think about it a bit more here

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Android upgrade ADT to 22 third party jar package caused by ClassNotFoundException and Noclassdeffounderror exception resolution