This happens when you open the Windows > Prefs > Android panel
while an SDK is initially loading or when you change the
SDK in the pref panel. The target change listener was not
properly removed since the field was not properly disposed.
This also removed the multiple selection handling in the
SdkTargetSelector, which we never use. In the unlikely event
we want to use it later, it would be trivial to add it back.
BUG=1793333
Automated import of CL 146631
For ADT #1603194, it is desirable to select the Instrumentation
Runner class from the android.jar. The class browser was filtering
it out. The class browser has been changed like this:
- include all source & jar package roots
- a checkbox let the user toggle between searching only sources
(of the project) or anything in the classpath (thus include jars.)
The default is to include everything for the instrumentation and only
the source for other browsers.
Also improved a bit the filter by not iterating over the hierarchy
and filtering out abstract classes (which was not needed before.)
BUG=1603194
Automated import of CL 146335
The fix I did last week was just refreshing the UiRootNode
but it turns out we need to refresh the DescriptorFilters too
(since they are null when there's no SDK.) So the old fix was
wrong, what we need is to generate a new tree model when the
SDK is reloaded.
BUG=1761064
Automated import of CL 146238
Bug description is to add support for <uses-configuration>.
Currently the Manifest editor already supports <uses-sdk> (which is an
element node, not an attribute) by exposing it as a manifest attribute.
That doesn't scale. So instead just provide a tree for all <manifest>
child elements that are not handled in other pages. Currently that
contains uses-sdk and uses-configuration but the nice part of it is that
it will pick up automatically any new manfiest sub elements in the future.
BUG=1789339
Automated import of CL 146237
It's really time to let the hackish bash/sed version go away,
especially since it's really really slow, and provide a
better python version instead.
BUG=1761137
Automated import of CL 145204
Issue: when the SDK gets (re)loaded, the uiRootNode changes
in the UiTreeBlock. However the TreeViewer is using a
content provider which root node was not updated. The fix is
to make the content provider dynamically ask for the root
node to the tree block. Instead of depending on the class
directly, a new interface is passed for this.
BUG=1761064
Automated import of CL 145004
The fix is that a menu contribution should redefine the menu that it is
contributing too. In this case it seems the JDT is not yet loaded or at
least hasn't defined the menu that we're contributing too, so we need to
define it. This definition is extracted from the jdt.ui/plugin.xml from
3.4 in order to define the same group names in the same order.
BUG=1722971
Automated import of CL 144940
Also renamed the container for add-ons to include the base platform name (so that at least a version is displayed).
BUG=1775936
Automated import of CL 144938
Activities that do not have an action, or that are set to not be exported cannot be launched from 'am start...' so they should not be considered when finding an activity to launch.
BUG=1736754
Automated import of CL 144366
That's a first pass. There's a fair bit of refactoring
involved, so it's split in two CLs. Next CL will add more
functionality.
BUG=1722971
Automated import of CL 144283
Rationale: we want to keep that code around, so we need to compile
it to make sure it doesn't use obsoleted APIs. That does it.
BUG=1743364
Automated import of CL 144048
This covers the case where an AVD has an invalid target
or is missing its AVD folder or the config.ini in it.
Made some cosmetic cleanup too.
BUG=1703143
Automated import of CL 143881
