I know I'm resurrecting an old thread, but I'm having the same problem. I don't know anyone that uses the same type of build for development, testing and release. I usually develop in Eclipse and have Ant targets that build a project for release without test cases, resources and libraries.
If I don't build from Ant, how can I be sure that my release APK doesn't include my test instrumentation and extra garbage? Thank you, Connor On May 26, 11:36 pm, Raphael <[email protected]> wrote: > On Tue, May 26, 2009 at 6:26 PM, Craig <[email protected]> wrote: > > > On May 26, 9:49 pm, Zero <[email protected]> wrote: > >> from my experience, eclipse never used the build.xml for it's internal > >> builds - how did you do that ? > > > The eclipse build doesn't use build.xml at all, but due to the fact > > that build.xml is in the eclipse project (because it is in the same > > directory as AndroidManifest.xml) eclipse tries to "build it" or at > > least parse it and check for errors. build.xml can't be parsed by > > eclipse (even though it is a valid file according to ant) and thus the > > android builder refuses to launch the project at all. This seems wrong > > to me. > > No it doesn't do that. > Would you have the Ant view open by any chance? Don't build from the > ant view if you build using Eclipse. > > R/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
