SdkManager: handle missing platforms/ and add-ons/ folders.

A while ago, when we were dealing with monolithics SDKs,
the strategy was that we wanted to make sure that
the 'android' command was invoked from a properly setup
SDK folder. Consequently the SdkManager required at least
the platforms/ and add-ons/ folders to be present, even if
empty.

I don't think that behavior is really necessary anymore.
The 'android' tool is invoked with knowledge from its tools
folder, so we can safely assume the top parent is "the SDK
folder" and create these directories if they are missing.

We do however try to create them as early as possible if
they are missing, so that the tool aborts early if we can't
create them. The other alternative would be to just try to
create them when we're actually installing a package.

Change-Id: I8ea58f23add89c2dac0a22142f6fb5e71b8203aa

1 files changed, 1 insertions, 1 deletions

diff --git a/sdkmanager/app/src/com/android/sdkmanager/internal/repository/AboutPage.java b/sdkmanager/app/src/com/android/sdkmanager/internal/repository/AboutPage.java
index cb2f981..4c72e1e 100755
--- a/sdkmanager/app/src/com/android/sdkmanager/internal/repository/AboutPage.java
+++ b/sdkmanager/app/src/com/android/sdkmanager/internal/repository/AboutPage.java
@@ -70,7 +70,7 @@ public class AboutPage extends Composite {
                 "Revision %1$s\n" +

                 "Add-on XML Schema #%2$d\n" +

                 "Repository XML Schema #%3$d\n" +

-                "Copyright (C) 2009-2010 The Android Open Source Project.",

+                "Copyright (C) 2009-2011 The Android Open Source Project.",

                 getRevision(),

                 SdkAddonConstants.NS_LATEST_VERSION,

                 SdkRepoConstants.NS_LATEST_VERSION));