I have been experiencing the same problem since updating everything earlier today. I read elsewhere that increasing the amount of memory to Eclipse could help, but it hasn't for me.
I'm thinking that library projects could be the culprit. I have three non-library projects that each depend on a single core library project. I noticed after performing the update that the linkedResources sections of the .project files of the non-library projects changed. The locationURIs changed - from "_android_MyLibrary/ src" to "_android_MyLibrary_ae53e0d6/src". I made a simple test app that doesn't depend on a library and it works fine. Building the project through Ant works just fine, so it seems to just be a problem with the Eclipse integration. I'm running Win XP Pro SP3 with Eclipse 3.5.2 and Oracle/Sun JDK 1.6.0_21. I have tried upgrading to Eclipse 3.6.1, uninstalling and cleanly reinstalling the SDK and plugin, adding the new tools and platform-tools directories to my PATH, removing and readding the library project links, and nothing works. Any idea how to fix this? Thanks, Adam (P.S. Sending to this group from Gmail doesn't seem to be working for me so I'm sending this from the Groups web interface. Sorry if this ends up being a double post). On Dec 6, 5:16 pm, Xavier Ducrohet <x...@android.com> wrote: > gotta love the error message. *sigh* > > From what you're saying you have all that's needed. Have you tried > using the Sun VM instead of OpenJDK? > We load dx.jar through reflection and it looks like calling out to a > method through reflection failed. > > Xav > > > > > > > > > > On Mon, Dec 6, 2010 at 2:33 PM, Tom Gibara <tomgib...@gmail.com> wrote: > > I upgraded to the 2.3 SDK and have hit a problem I can't resolve. > > > First I updated the android plugins for eclipse (3.5.2) to the new > > version (8.0.0.v201011171904-77661). Then I used the SDK manager > > within eclipse to install the Android SDK 2.3 API 9 package, its > > documentation, and the Android SDK platform tools revision 1. > > > On restarting eclipse I found that every non-library android project > > was reporting the same error: > > > [2010-12-06 21:58:32 - Dex Loader] Unable to execute dex: null > > [2010-12-06 21:58:32 - ] Conversion to Dalvik format > > failed: Unable to execute dex: null > > > I have tried cleaning the projects, reinstalling the plugins and > > changing the declared SDK location. I have confirmed that eclipse has > > the latest plugin, that the platform-tools directory exists, as does > > the platforms/android-9 directory, and that they contain the correct > > files. I switched the plugin into "verbose" for building, but can't > > see anything remotely suspicious. I can even run dx manually on the > > project bin directory and produce a classes.dex file. > > > I'm stumped, does anyone have any ideas? > > > This is on a 32-bit Ubuntu (Lucid Lynx) machine with OpenJDK (IcedTea6 > > 1.8.2) (6b18-1.8.2-4ubuntu2) (build 16.0-b13, mixed mode) > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to android-developers@googlegroups.com > > To unsubscribe from this group, send email to > > android-developers+unsubscr...@googlegroups.com > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en > > -- > Xavier Ducrohet > Android SDK Tech Lead > Google Inc. > > Please do not send me questions directly. Thanks! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
