Hi Kaloyan,
Thank you for doing this. I just don't have time these days. I'll try to test later in the week when I'm back home.
I always wondered why those divisions were in there when Google maintained the package. They seem somewhat arbitrary other than the NDK one. It doesn't bother me that they are like that now, but we should have some conversation around those divisions in the future.
Do we do this by plugin functionality as they are partially done at the moment or by user profile. I think the download packages are meant for user profiles but we sometimes get blinded by choice of language (CDT, JDT, PHP, etc.). If we get too much segmentation, we confuse new users. Too little segmentation and it's too opaque or we have a monolithic download.
At Motorola, as we were nearing the end of the Motodev project, we wanted to split out the plugins from the Android SDK requirements. It was always a pain when a new set of ADT plugins came out because some of the signatures would change or features we relied on would end up in a private namespace. We separated our features into those that could be used independent of ADT and SDK and those that relied on them. The Core plugins could be installed into any Eclipse while our addons had to be built and linked into the branded Motodev tools. Not ideal, but we wanted people using our plugins regardless of how they were packaged. Now the better parts of Motodev Studio are in Andmore, so we just need to segment the features in a way that makes sense.
-E