title: Android SDK manager fails, if launched from Eclipse
body: <p>Has anyone seen this problem? </p>
  
  <p>I'm in the middle of updating my SDK to add Android 2.2, on my Mac.
  You don't have to download the entire SDK -- there is a tool already on your system which can download just the extra parts of Adroid 2.2  This page explains: <a href="http://developer.android.com/sdk/adding-components.html" rel="nofollow noreferrer">http://developer.android.com/sdk/adding-components.html</a></p>
  
  <p>The tool is called the "Android SDK and AVD manager".    There are two ways to start this tool. </p>
  
  <ol>
  <li>You can start it from within Eclipse, via: Window > "Android SDK and AVD Manager"</li>
  </ol>
  
  <p>or</p>
  
  <ol start="2">
  <li>You can start it from the command line, via  cd /tools ; ./android &amp;</li>
  </ol>
  
  <p>To my surprise, the tool is slightly different, when started from the different places.  In particular, starting it from Eclipse, and pressing the "Available Packages" button, did NOT show the new Android 2.2 release.  Starting it from the command line <em>does</em> show the new Android 2.2 release, and enables me to install it.</p>
  
  <p>It's very easy to install the 2.2 update, but you have to start the SDK manager from the command line on Mac.  It looks like all the downloads will take a hour or two.</p>
  
  <p>Has anyone else noticed this problem, and what is the place to report Android tools bugs?</p>