Please see: http://groups.google.com/group/android-developers/msg/6506f3c12c8e4d73
The solution is to edit the project containing the code to only be "library" project. This is a concept we don't support yet, but you can make them manually by editing .project to remove the Android nature and builder (in the message I linked I mistakenly mention editing .classpath when it's .project you need to edit). Xav On Mon, May 18, 2009 at 4:46 PM, Peter Jeffe <[email protected]> wrote: > > Our app is build from three eclipse projects, one of which contains > the Android app manifest, and which includes the other two projects. > Previously this worked just fine, but after upgrading to the 1.5 SDK, > building against a 1.1 target, it now doesn't seem to include the > other projects in the .apk at build time, so now I get "dalvikvm: > Could not find method X" errors when I try to run the app. > > BTW this sounds like the same problem that was reported in this > thread: > http://groups.google.com/group/android-developers/browse_thread/thread/c5ff11e57b344e89/abfd32e61a3e3770 > > This is a big problem, we have very good reasons for wanting to keep > these as separate projects, so can someone please suggest a way to > make this work? > > -- Peter > > > -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
