Further, it's not just release builds that have such a requirement; continuous build systems need to be able to build without a GUI app.
On Jul 19, 1:25 pm, MrSqueezles <[email protected]> wrote: > Normally, when I develop an application, I develop in Eclipse. I test > in both Eclipse and Ant. Then, I use Ant to package the application > for release, excluding test classes, test libraries and test > resources. I created a build.xml in my Android Eclipse project, > though, and got a project error because of the strange > "android_rules.xml" setup. After much searching, I found this > explanation. > > "That's kind of an unexpected workflow. The idea is that either you go > the full way in Eclipse or you use Ant/DDMS. Trying to combine both is > a recipe for confusion :-)" > > I'm not sure to what confusion the author was referring. I've always > used both Eclipse and Ant together. Eclipse even has an Ant view > specifically designed to run Ant tasks in a build.xml. It would be > great to use only Eclipse, but how can I fine tune my release build to > be sure that my APK doesn't include my test cases, libraries, > resources and, maybe most importantly, instrumentation? > > Thanks in advance, > Connor --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
