Android SDK Tools R17发布

Revisions

The sections below provide notes about successive releases of the SDK Tools, as denoted by revision number. To determine what revision of the SDK Tools you are using, refer to the "Installed Packages" listing in the Android SDK Manager.

For a summary of all known issues in SDK Tools, see http://tools.android.com/knownissues.

SDK Tools, Revision 17(March 2012)

Important: To download the new Android 4.0 system components from the Android SDK Manager, you must first update the SDK tools to revision 14 or later and restart the Android SDK Manager. If you do not, the Android 4.0 system components will not be available for download.

Dependencies:

• Android SDK Platform-tools revision 9 or later.
• If you are developing in Eclipse with ADT, note that the SDK Tools r17 is designed for use with ADT 17.0.0 and later. If you haven't already, we highly recommend updating yourADT Plugin to 17.0.0.
• If you are developing outside Eclipse, you must have Apache Ant 1.8 or later.

General notes:

• Emulator
  • Added support for hardware accelerated graphics rendering. This feature requires an API Level 15, Revision 3 or later system image. (more info)

    Note: As of the SDK Tools Revision 17 release, the API Level 15, Revision 3 system image is not yet available.

  • Added support for running Android x86 system images in virtualization mode on Windows and Mac OS X. (more info)
  • Added experimental support for multi-touch input by enabing the emulator to receive touch input from a USB-tethered physical Android device. (more info)
• Added viewing of live detailed network usage of an app in DDMS. (more info)
• ProGuard
  • Updated the bundled ProGuard tool to version 4.7. In addition to many new features, this update fixes theConversion to Dalvik format failed with error 1 error some users have experienced.
  • Updated the default proguard.cfg file with better default flags for Android.
  • Split the ProGuard configuration file has been in half, with project specific flags kept in project and the generic Android flags distributed (and updated) with the tools themselves.
• Build
  • Added a feature that allows you to run some code only in debug mode. Builds now generate a class calledBuildConfig containing a DEBUG constant that is automatically set according to your build type. You can check the (BuildConfig.DEBUG) constant in your code to run debug-only functions.
  • Fixed issue when a project and its libraries include the same jar file in their libs folder. (more info)
  • Added support for custom views with custom attributes in libraries. Layouts using custom attributes must use the namespace URIhttp://schemas.android.com/apk/res-auto instead of the URI that includes the app package name. This URI is replaced with the app specific one at build time.
• Lint
  • Updated Lint to check Android application code. Lint rules which previously performed pattern based searches in the application code (such as the unused resource check) have been rewritten to use the more accurate Java-style parse trees.
  • Added support for checking library projects. This change means that rules such as the unused resource check properly handle resources declared in a library project and referenced in a downstream project.
  • Added ability to suppress Lint warnings in Java code with the new@SuppressLint annotation, and in XML files with the new tools: namespace and ignore attribute. (more info)
  • New Lint checks:
    • Added check for Android API calls that require a version of Android higher than the minimum supported version. You can use the new@TargetApi annotation to suppress warnings when the code is wrapped in a system version condition. (more info)
    • Added over 20 new Lint rules, including checks for performance, XML layouts, manifest and file handling.