1) I think this problem is solely related to using external JAR's. I tried to do reference an external JAR for the first time, and got exactly the same error. If you have solved this issue, please post.
2) Sorry, don't know about this. Thanks, JIm On Nov 19 2008, 2:50 pm, Alvin Yates <mamboth...@gmail.com> wrote: > I'm making a new project where I'm attempting to share onlycommon > Javacode(i.e. no Android classes used) that handle boring stuff like > data structures, data formatting, and XML parsing from my previous > Android app. You know, stuff that I would eventually like to go back > and refactor to be properly done. > > I had an issue with making anEclipselibrary and importing that into > a project (Runtime validation errors, which I solved by importing each > JAR file for HTTP MIME separately), and I seem to be having an equally > lame issue right now. Adding the previous project's source to my > build path gives this error: > > [2008-11-19 12:24:58 - Dex Loader] Unable to execute dex: null > [2008-11-19 12:24:58 - MyApp] Conversion to Dalvik format failed: > Unable to execute dex: null > > So a few questions come to mind: > > 1) What is this error referring to? Is this a problem with my > Manifest (which is in a different library), or a limitation on how > theEclipseplug-in works with the DVM? > > And the more general... > > 2) Is creating usercommoncodepossible withinEclipsesuch that > Dalvik will not cause some error in compile/runtime validation? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
