title: Unable to debug library project
body: <p>I just upgraded to the latest Android SDK tools. Now when I set a break point in a library project and the breakpoint is hit I just get a blank .class file and can no longer debug or step the source code. What do I need to do to fix the latest SDK tools to add back support for debugging library projects?</p>
  
  <p>At this point there appears to be no way to debug a library project at all?</p>
  
  <p>.classpath file</p>
  
  <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
  &lt;classpath&gt;
      &lt;classpathentry kind="con" path="com.android.ide.eclipse.adt.ANDROID_FRAMEWORK"/&gt;
      &lt;classpathentry kind="con" path="com.android.ide.eclipse.adt.LIBRARIES"/&gt;
      &lt;classpathentry kind="src" path="src"/&gt;
      &lt;classpathentry kind="src" path="gen"/&gt;
      &lt;classpathentry kind="output" path="bin/classes"/&gt;
  &lt;/classpath&gt;
  </code></pre>
  
  <p>None of the items in this class path seem to correspond to the library project that I am including. This is the class path of the main project, not the library project.</p>
  
  <p>Does anyone know of any new documentation for how to do library projects that came out since the latest tools release? The existing documentation seems to no longer be valid. I used to be able to step and debug any library that was included into a top level Android App. So to fully test a library I could do it through the delivery main app. But now it seems that can no longer be done. </p>
  
  <p>Do I need to set the library to not be a library, then debug and test the library stand alone, then set the library back to being a library right before I deliver? This seems like the SDK has been crippled since the last release. </p>