Fixed
Status Update
Comments
jb...@google.com <jb...@google.com> #2
This isn't actually true in general: it just happened coincidentally because the legacy sdk support thinks a package in a directory called "tools" is the "tools" package, specifically. If the package is in a place not hardcoded into the legacy sdk support it won't be recognized at all.
jb...@google.com <jb...@google.com> #3
Fix is checked in, but probably won't be out until the release after the upcoming one.
Description