在eclipse配置了ADT，但是导入第一个项目的时候报错右键项目选择properites提示有这些错误
Finds API accesses to APIs that are not supported in all targeted API versionsThis check scans through all the Android API calls in Finds method declarations that will accidentally override methods in later versionsSuppose you are building against Android API 8, and you've subclassed Activity. In your subclass you add a new method called isDestroyed(). At some later point, a method of the same name and signature is added to Android. Your method will now override the Android method, and possibly break its contract. Your method is not calling super.isDestroyed(), since your compilation target doesn't know about the method.The above scenario is what this lint detector looks for. The above example is real, since isDestroyed() was added in API 17, but it will be true for any method you have added to a subclass of an Android class where your build target is lower than the version the method was introduced in.To fix this, either rename your method, or if you are really trying to augment the builtin method if available, switch to a higher build target where you can deliberately add @Override on your overriding method, and call super if appropriate etc.This check scans through libraries looking for calls to APIs that are not included in Android.When you create Android projects, the classpath is set up such that you can only access classes in the API packages that are included in Android. However, if you add other projects to your libs/ folder, there is no guarantee that those .jar files were built with an Android specific classpath, and in particular, they could be accessing unsupported APIs such as java.applet.This check scans through library jars and looks for references to API packages that are not included in Android and flags these. This is only an error if your code calls one of the library classes which wind up referencing the unsupported package.
Looks for cycles in style definitionsThere should be no cycles in style definitions as this can lead to runtime exceptions.
Checks that AdapterViews do not define their children in XMLAdapterViews such as ListViews must be configured
Finds API accesses to APIs that are not supported in all targeted API versionsThis check scans through all the Android API calls in Finds method declarations that will accidentally override methods in later versionsSuppose you are building against Android API 8, and you've subclassed Activity. In your subclass you add a new method called isDestroyed(). At some later point, a method of the same name and signature is added to Android. Your method will now override the Android method, and possibly break its contract. Your method is not calling super.isDestroyed(), since your compilation target doesn't know about the method.The above scenario is what this lint detector looks for. The above example is real, since isDestroyed() was added in API 17, but it will be true for any method you have added to a subclass of an Android class where your build target is lower than the version the method was introduced in.To fix this, either rename your method, or if you are really trying to augment the builtin method if available, switch to a higher build target where you can deliberately add @Override on your overriding method, and call super if appropriate etc.This check scans through libraries looking for calls to APIs that are not included in Android.When you create Android projects, the classpath is set up such that you can only access classes in the API packages that are included in Android. However, if you add other projects to your libs/ folder, there is no guarantee that those .jar files were built with an Android specific classpath, and in particular, they could be accessing unsupported APIs such as java.applet.This check scans through library jars and looks for references to API packages that are not included in Android and flags these. This is only an error if your code calls one of the library classes which wind up referencing the unsupported package.
Looks for cycles in style definitionsThere should be no cycles in style definitions as this can lead to runtime exceptions.
Checks that AdapterViews do not define their children in XMLAdapterViews such as ListViews must be configured
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货