Eclipse is an open source community. Find downloads for packages, developer builds, and projects. In preparation for installing the 3.1.0 Beta SDK, I inadvertently re-installed the Eclipse CIQ plugin, and now I only have the 3.1.0 SDK in my SDK manager: I need to be able to return to 3.0.12 to release my app. Eclipse is still using 3.0.12 because I have not yet taken the 'Use as SDK' option on 3.1.0.
Details Group Tabs
Android Development Tools (ADT) is a plugin for the Eclipse IDE that is designed to give you a powerful, integrated environment in which to build Android applications.
ADT extends the capabilities of Eclipse to let you quickly set up new Android projects, create an application UI, add packages based on the Android Framework API, debug your applications using the Android SDK tools, and even export signed (or unsigned) .apk files in order to distribute your application.
Developing in Eclipse with ADT is highly recommended and is the fastest way to get started. With the guided project setup it provides, as well as tools integration, custom XML editors, and debug output pane, ADT gives you an incredible boost in developing Android applications.
- Mobile apps,
|May 2021||91/728||141 (0.17%)||4|
|April 2021||129/914||579 (0.12%)||28|
|March 2021||117/918||672 (0.13%)||38|
|February 2021||118/911||552 (0.13%)||38|
|January 2021||102/930||698 (0.15%)||52|
|December 2020||109/919||603 (0.14%)||38|
|November 2020||128/925||544 (0.12%)||38|
|October 2020||124/927||590 (0.13%)||37|
|September 2020||169/894||304 (0.07%)||26|
|August 2020||199/867||173 (0.05%)||25|
|July 2020||184/870||223 (0.05%)||35|
|June 2020||177/867||265 (0.06%)||26|
Unsuccessful Installs in the last 7 Days: 3
|2||Cannot complete the install because of a conflicting dependency..|
|1||Cannot complete the install because of a conflicting dependency..|
In this document
- Installing the ADT Plugin
Android Development Tools (ADT) is a plugin for the Eclipse IDEthat is designed to give you a powerful, integrated environment in whichto build Android applications.
ADT extends the capabilities of Eclipse to let you quickly set up new Androidprojects, create an application UI, add components based on the AndroidFramework API, debug your applications using the Android SDK tools, and evenexport signed (or unsigned) APKs in order to distribute your application.
Developing in Eclipse with ADT is highly recommended and is the fastest wayto get started. With the guided project setup it provides, as well as toolsintegration, custom XML editors, and debug ouput pane, ADT gives you anincredible boost in developing Android applications.
This document provides step-by-step instructions on how to download the ADTplugin and install it into your Eclipse development environment. Note thatbefore you can install or use ADT, you must have compatible versions of both theEclipse IDE and the Android SDK installed. For details, make sure to read Installing the ADT Plugin, below.
If you are already using ADT, this document also provides instructions onhow to update ADT to the latest version or how to uninstall it, if necessary.
The sections below provide notes about successive releases ofthe ADT Plugin, as denoted by revision number.ADT 9.0.0(January 2011)
- 'Go To Declaration' hyperlink support: You can jump directly from code references (such as
R.id.main) to the corresponding XML declaration, or from XML attributes (such as
@string) to the corresponding resource definition, or from manifest XML registrations to activities and services.
- Improvements were made to name refactoring.
- AVDs now automatically save their state, so they can restart almost instantly. You can enable this feature when creating an AVD or by editing an AVD with the AVD Manager.
- Improvements to the Visual Layout Editor:
- Support for rendering targets: You can now choose an arbitrary Android platform to render the current page, regardless of the project's minimum platform. This makes it easy to verify the layout and appearance of your activity on different versions of the platform.
- Improved support for empty and nested layouts: Dragging items over nested and invisible layouts automatically enlarges and highlights these layouts, so that they can receive drops.
- XML formatting improvements: The editor generates cleaner XML and you can now enable XML auto-formatting in the Preferences menu.
- Improved Outline labels: The Outline tab now displays additional information about each View. Textual Views display a snippet of the actual text. Views with a source (such as ImageView) displays the resource name. Included Views display the name of the View.
- When you right click a View in the Layout Editor, the context menu now contains Edit ID.. and Edit Text.. items. The Properties.. context menus now list all of the properties and provide a way to edit them (Details).
- The layout editor now properly handles
- 'Extract as Include' refactoring: The Layout Editor has a new refactoring that allows you to select one or more views in a layout, and extract it into a separate layout (Details).
- Improved diagnostics for class loading and rendering errors: Class loading and rendering error messages are more useful and provide better information about the root cause of the error.
- Improved error handling to prevent drag and reordering operations from adding children into an
- Outline reordering: Reordering your views in the Outline tab is much easier (Details).
- Fix for keybinding bug where keyboard shortcuts did not work (Issues 13231 and 13134).
- Fix for problems with Custom layout attribute menu (Issue 13134).
- Automatic configuration for various view types: Certain views have properties configured by default. For example, the width of an
EditTextobject is set to
match_parentwhen added to a vertical
LinearLayoutor a default image is added to an
- Previews during dragging: Dragging from the palette or dragging within the layout editor now shows live previews of the dragged item.
- Navigation improvements: In the Layout Editor, double-clicking Views jumps to the corresponding XML element. In the Outline view, double-clicking opens the Properties view.
- The editor has Honeycomb style animation preview support.
- Improved rendering support for various Views (such as TabHosts and SlidingDrawers) in Honeycomb (Issues 3162 and 13092).
- Included layouts can be rendered and edited in the context of the layouts that include them. From a layout using an
<include>tag, double-clicking on the
<include>element edits the referenced layout in the context of the current layout. Additionally, when editing a layout that is included by other layouts, you can quickly change between context layouts, by right clicking in the editor and choosing Show included in... This feature is only available in Honeycomb.
- This release fixes many other bugs, but the most important ones are listed below:
- Fixed issue that prevented launching debug builds on productions devices when
debuggable=truewas not set in the Android manifest.
- The LogCat view in DDMS properly handles UTF-8 characters.
- The SDK Manager is more reliable on Windows (Details).
- A JUnit initialization bug that prevented you from working with JUnit tests was fixed (Issue 12411).
- Fixed issue that prevented launching debug builds on productions devices when
ADT 8.0.1 is designed for use with SDK Tools r8. If you haven'talready installed SDK Tools r8 into your SDK, use the Android SDK and AVD Manager to doso.
- This is a quick follow-up to ADT 8.0.0 to fix some bugs.
- Fixes an issue in which projects failed to compile, citing a dex error.
- Better ProGuard error reporting when exporting applications for release.
Also see the recent release notes for 8.0.0, below.ADT 8.0.0(December 2010)
ADT 8.0.0 is designed for use with SDK Tools r8. If you haven'talready installed SDK Tools r8 into your SDK, use the Android SDK and AVD Manager to doso.
- New version number scheme that follows the SDK Tools revision number. The major versionnumber for your ADT plugin should now always match the revision number of your SDK Tools. Forexample, ADT 8.x is for SDK Tools r8.
- Support for true debug build. You no longer need to change the value of the
debuggableattribute in the Android Manifest.
Incremental builds automatically insert
debuggable='true', but if you perform 'export signed/unsigned application package', ADT does not insert it. If you manually set
debuggable='true'in the manifest file, then release builds will actually create a debug build (it does not remove it if you placed it there).
- Automatic ProGuard support in release builds. For it to work, you need to have a
proguard.configproperty in the
default.propertiesfile that points to a ProGuard config file.
- Completely rewritten Visual Layout Editor. (This is still a work in progress.) Now includes:
- Full drag and drop from palette to layout for all Layout classes.
- Move widgets inside a Layout view, from one Layout view to another and from one layout file to another.
- Contextual menu with enum/flag type properties.
- New zoom controls.
- New HierarchyViewer plug-in integrated in Eclipse.
- Android launch configurations don't recompile the whole workspace on launch anymore.
android.jarsource and javadoc location can now be configured.
ADT 0.9.9 replaces ADT 0.9.8 and is designed for use with SDK Tools r7and later. ADT 0.9.9 includes the ADT 0.9.8 features as well as an importantbugfix, so we recommend that you upgrade as soon as possible. If you haven'talready installed SDK Tools r7 into your SDK, use the Android SDK Manager to doso.
- Fixes a problem in project import, in which source files were deleted in some cases.
- Includes all other ADT 0.9.8 features (see below).
ADT 0.9.8 is now deprecated. Please use ADT 0.9.9 instead.
- Adds a new Action, 'Rename Application Package', to the Android Toolscontextual menu. The Action does a full application package refactoring.
- Adds support for library projects that don't have a source foldercalled
src/. There is now support for any number of source folders,with no name restriction. They can even be in subfolder such as
src/java. If you are already working with library projects createdin ADT 0.9.7, see Migratinglibrary projects to ADT 0.9.8 for important information about movingto the new ADT environment.
- Adds support for library projects that depend on other libraryprojects.
- Adds support for additional resource qualifiers:
- Adds more device screen types in the layout editor. All screenresolution/density combinations listed in the SupportingMultiple Screens are now available.
- Fixes problems with handling of library project names thatcontain characters that are incompatible with the Eclipse path variable.Now properly sets up the link between the main project and the libraryproject.
The ADT Plugin now supports the use of library projects duringdevelopment, a capability that lets you store shared Android applicationcode and resources in a separate development project. You can then reference thelibrary project from other Android projects and, at build time, the toolscompile the shared code and resources as part of the dependent applications.More information about this feature is available in the Developingin Eclipse with ADT document.
If you are not developing in Eclipse, SDK Tools r6 provides the equivalent libraryproject support through the Ant build system.ADT 0.9.6(March 2010)
ADT 0.9.6 is designed for use with SDK Tools r5 and later. Beforeupdating to ADT 0.9.6, we highly recommend that you use the Android SDK andAVD Manager to install SDK Tools r5 into your SDK.
default.propertiesoutside of Eclipse will nowautomatically update the project.
- Loads the SDK content only when a project requires it. This will makeEclipse use less resources when the SDK contains many versions of Android.
- Resolves potential deadlock between modal dialogs, when launching ADT thefirst time with the SDK Usage panel.
- Fixes issues with the New Project Wizard when selecting samples.
- Adds support for platform samples components.
- Improves support for dependency between components.
- AVDs now sorted by API level.
- The AVD creation dialog now enforces a minimum SD card size of 9MB.
- Prevents deletion of running AVDs.
- DDMS plug-in now contains the Allocation Tracker view.
- New action in the Logcat view: 'Go to problem' lets you go directly from anexception trace output to the code.
- Explode mode in the Visual Layout Editor adds a margin to all layout objectsso that it's easier to see embedded or empty layouts.
- Outline mode in the Visual Layout Editor draws layout outline to make iteasier to see layout objects.
- Several fixes in the configuration selector of the Visual LayoutEditor.
- Applications launched from ADT now behave as if they were clicked from theHome screen.
- Fixes issue where add-on with no optional library would not show up as validtargets for application launches.
- Resolves possible crash when launching applications.
ADT 0.9.5 requires features provided in SDK Tools r4 or higher. If you installADT 0.9.5, which is highly recommended, you should use the Android SDK and AVDManager to download the latest SDK Tools into your SDK. For more information,see Adding SDK Components.
- AVD Launch dialog now shows scale value.
- Fixes potential NPE in SDK Manager on AVD launch, for older AVD with no skin name specified.
- Fixes XML validation issue in on older Java versions.
- .apk packaging now properly ignores vi swap files as well as hidden files.
ADT 0.9.4 requires features provided in SDK Tools r3 or higher. If you installADT 0.9.4, which is highly recommended, you should use the Android SDK and AVDManager to download the latest SDK Tools into your SDK. For more information,see Adding SDK Components.
- New option to create a project from a sample by choosing it from a list.
- Improved Configuration selector that lets you see how your layout willrender on different devices. Default device descriptions include ADP1and Google Ion, while SDK add-ons can also provide new descriptions.A new UI allows you to create custom descriptions.
- Adds a new clipping toggle, to let you see your full layout even if it'sbigger than the screen.
- Includes the improvements from the standlone DDMS, revision 3.
- Adds an option to open HPROF files into eclipse instead of writing them ondisk. If a profiler such as MAT (Memory AnalyzerTool) is installed, it'll open the file.
- Includes the improvements from the standalone Android SDK and AVD Manager,revision 3.
Installing the ADT Plugin
The sections below provide instructions on how to download and installADT into your Eclipse environment. If you encounter problems, see the Troubleshooting section.
Preparing Your Development Computer
ADT is a plugin for the Eclipse IDE. Before you can install or use ADT,you must have a compatible version of Eclipse installed on your developmentcomputer.
- If Eclipse is already installed on your computer, make sure that it isa version that is compatible with ADT and the Android SDK. Check the System Requirements document fora list of Eclipse versions that are compatible with the Android SDK.
- If you need to install or update Eclipse, you can download it from thislocation:
For Eclipse 3.5 or newer, the 'Eclipse Classic' version is recommended. Otherwise, a Java or RCPversion of Eclipse is recommended.
Additionally, before you can configure or use ADT, you must install theAndroid SDK starter package, as described in Downloading the SDK Starter Package.Specifically, you need to install a compatible version of the Android SDK Toolsand at least one development platform. To simplify ADT setup, we recommendinstalling the Android SDK prior to installing ADT.
Download Eclipse For Windows 10
When your Eclipse and Android SDK environments are ready, continue with theADT installation as described in the steps below.
Downloading the ADT Plugin
Use Update Manager feature of your Eclipse installation to install the latestrevision of ADT on your development computer. $10 off jiffy lube coupon.
Assuming that you have a compatible version of the Eclipse IDE installed, asdescribed in Preparing for Installation, above, followthese steps to download the ADT plugin and install it in your Eclipseenvironment.
|Eclipse 3.5 (Galileo) and 3.6 (Helios)||Eclipse 3.4 (Ganymede)|
Configuring the ADT Plugin
Once you've successfully downloaded ADT as described above, the next stepis to modify your ADT preferences in Eclipse to point to the Android SDK directory:
- Select Window > Preferences.. to open the Preferences panel (Mac OS X: Eclipse > Preferences).
- Select Android from the left panel.
- For the SDK Location in the main panel, click Browse.. and locate your downloaded SDK directory.
- Click Apply, then OK.
Done! If you haven't encountered any problems, then the installation iscomplete. If you're installing the Android SDK for the first time, return to Installing the SDK to complete your setup.
Troubleshooting ADT Installation
If you are having trouble downloading the ADT plugin after following thesteps above, here are some suggestions:
- If Eclipse can not find the remote update site containing the ADT plugin,try changing the remote site URL to use http, rather than https. That is, setthe Location for the remote site to:
- If you are behind a firewall (such as a corporate firewall), make sure thatyou have properly configured your proxy settings in Eclipse. In Eclipse,you can configure proxy information from the main Eclipse menu inWindow (on Mac OS X, Eclipse) >Preferences > General > NetworkConnections.
If you are still unable to use Eclipse to download the ADT plugin as aremote update site, you can download the ADT zip file to your local machine andmanually install it:
- Download the current ADT Plugin zip file from the table below (do not unpack it).
Name Package Size MD5 Checksum ADT 9.0.0 ADT_9.0.0.zip 4433536 bytes bc2757f2a5a11d131390ce547bae154b
- Follow steps 1 and 2 in the default install instructions (above).
- In the Add Site dialog, click Archive.
- Browse and select the downloaded zip file.
- Enter a name for the local update site (e.g., 'Android Plugin') in the 'Name' field.
- Click OK.
- Follow the remaining procedures as listed for default installation above, starting from step 4.
To update your plugin once you've installed using the zip file, you will haveto follow these steps again instead of the default update instructions.
Other install errors
Note that there are features of ADT that require some optionalEclipse components (for example, WST). If you encounter an error wheninstalling ADT, your Eclipse installion might not include these components.For information about how to quickly add the necessary components to yourEclipse installation, see the troubleshooting topicADTInstallation Error: 'requires plug-in org.eclipse.wst.sse.ui'.
For Linux users
If you encounter this error when installing the ADT Plugin for Eclipse:
..then your development machine lacks a suitable Java VM. Installing SunJava 6 will resolve this issue and you can then reinstall the ADTPlugin.
Updating the ADT Plugin
From time to time, a new revision of the ADT Plugin becomes available, withnew features and bug fixes. Generally, when a new revision of ADT is available,you should update to it as soon as convenient.
Android Sdk Eclipse
In some cases, a new revision of ADT will have a dependency on a specificrevision of the Android SDK Tools. If such dependencies exist, you will need toupdate the SDK Tools component of the SDK after installing the new revision ofADT. To update the SDK Tools component, use the Android SDK and AVD Manager, asdescribed in Adding SDK Components.
To learn about new features of each ADT revision and also any dependencies onthe SDK Tools, see the listings in the Revisionssection. To determine the version currently installed, open theEclipse Installed Software window using Help> Software Updates and refer to the version listed for'Android Development Tools'.
Nordic Sdk Eclipse
Follow the steps below to check whether an update is available and, if so,to install it.
|Eclipse 3.5 (Galileo) and 3.6 (Helios)||Eclipse 3.4 (Ganymede)|
If you encounter problems during the update, remove the existing ADT plugin from Eclipse, thenperform a fresh installation, using the instructions for Installing the ADTPlugin.