Android development package introduction (ADT17)

Update the latest ADT plug-in. There is no exception in the packaging project, but the imported jar package cannot be found while the program is running.

Updating the latest ADT plug-in does not cause any exception in the packaging project, but the imported jar package cannot be found while the program is running. when updating the latest ADT plug-in, you will naturally encounter such a problem. (Because the sdk is updated to 1.7 or above, you need to update the ADT plug-in of eclipse to the latest 17 or above ). However, the ADT plug-in package introduction method has changed.

First, the project you built naturally has an Android Dependencie package. (Do not delete this package. If it is deleted, it cannot be found. At least I have not found a solution yet)

All imported packages will be backed up under the Android Dependencie package.

The imported package must also be placed in the libs directory of the root directory under the specified directory. Otherwise, the package cannot be found.

Before ADT17, to introduce an External JAR package to the Android project, you only need to select Add External JARs in the Java Build Path of the Project attribute, and then select the corresponding JAR package. However, after the upgrade to ADT17, the Android project has an additional Android Dependencies directory. The jar package added by adding External JARs still appears under the Referenced Libraries directory, however, it seems that it has been discarded. Although no error is prompted, ClassNotFoundException will be thrown at runtime. The solution is to add the JAR package to Android Dependencies. One of the default import directories is libs. Therefore, you only need to copy the JAR package to this directory.

 

From the wanli_smile Column