Ext: An easy solution to eclipse prompts for an ADT version too low after updating the Android SDK

Thanks to GFW, there will always be some puzzling questions for the beginner.

Let's start with the "historical reasons" for this blog post, because after updating the SDK, when I go to eclipse to set up the Android SDK directory, I suddenly say my version is low or something, try to solve it myself but failed, I found a lot of Chinese information on the search engine, But did not find a real solution to the problem, a few hours later, I gave up, so turned out in English to find a bit, sure enough to find a solution! I have a few questions about this: 1. Do domestic developments stop on the lower version of the system? 2. Is the SDK not updated in domestic development? 3 There is no data to share or to discuss the solution?
These three questions are purely grumbling, so let's get down to business. Add a note, the following circumstances only I and my computer encountered, not generic, for reference only.

First a picture, update in

Update to API12 when there is a problem, this time will inevitably appear, but my version is really all ah, wow ka ka ~
Here, there is an easy way (scheme one), is to change the latest version of Eclipse, the problem is resolved!! If you do not want to change, please continue to look down.

The update is successful, but after the Android SDK update, Eclipse will suddenly have to reset the SDK directory, and at the time of setup, there will be a problem

In addition, the ADT 10.0.0 or higher version is not so easy to get, (at least my network conditions have not reached, from the existing eclipse is very difficult to update), and, do not set up the SDK directory, Android SDK Manager does not work properly, So we have to handle it manually ~ ~ First on the key place map ~

After the update you can see that there is a problem, 10.0.0, yes, that's it.

After each update, the phrase "Plugin.prop" in the%android_home%\tools\lib directory becomes 10.0.0, if not changed, the system will consider the version is too low, to use the lower version of Eclipse development, as long as the change to " plugin.prop.plugin.version=9.0.0 "can. (Wordy,%android_home% is the directory where the SDK is located OH)

Here's a picture.

Yes, it's so simple, change it, then restart Eclipse, go into the setup is OK ~

The problem is simply solved (scenario two is over) this may be a lazy approach, but should be suitable for a later version of the update problem, or the time of the 20.0.0, then, or change, you can let the old version of Eclipse or ADT support the new SDK ~ ~ ~ OR, In Linux, it is also suitable, because I also encountered the same problem in Linux, but also solved the ~

Ext: An easy solution to eclipse prompts for an ADT version too low after updating the Android SDK