Eclipse and the Java Development Kit used by Eclipse has approximately nothing to do with your development, with the development of an Android Application using the standard SDK.

To clarify this point you can consider 3 important facts:

• you can build a complete Android App from the source without using Eclipse


• Eclipse is only an IDE for the Android SDK, a group of graphical elements that can speed up your workflow, nothing more and nothing less


• Eclipse uses a JDK environment when the Android SDK does not ( the A. SDK uses nothing else rather then the SDK itself ), they simply use different environments to run and build apps, so it's simply misleading saying something like "Eclipse not using dual core when compiling a huge Android project"

I think that at this point should be clear the fact that your app is actually compiled by the SDK itself and what you are stressing as bad thing is usually referred as a good thing.

Multithreaded application and, in general, application ( with "application" right now i mean the SDK not your app ) that supports their execution splitted in several jobs, brings a big problem on the table: a good and effective debugging phase.
Let's say that you are compiling something splitted in 4 threads, in the istant X your compiler crash, the question is: which of the 4 is the bad guy? all of them? just 1? 2? 3?

Considering that a tipical use of the Android SDK is not heavily based on multi-threaded design ( with that i mean that a developer can wait 1 or 2 minutes in the worst case scenario, nothing changes and the debug in multi-threaded environment with some concurrency on the go is much more complex and can take you weeks without achieving any results ), the adoption of a multi-threaded design can easily provide more cons than pros, especially during the phase of compiling and debugging.

In the end considering the audience of developers, the target of Android, what an Android application really is, this kind of software design is probably the most appropriate and effective and i will not considering the lack of a multi-threading compiling a bad thing.