I don't have a good answer for this, but I did go through the same thing as you. I recently published 6 apps on the same codebase with a few differing assets. I did it by refactoring in Eclipse, just like you mentioned.
On May 25, 3:51 pm, Jonathan Johnson <[email protected]> wrote: > I asked this on Stackoverflow, and got my first tumbleweed, so I > thought I would give it a chance here. :) > > I'm building a suite of applications, meaning that I have a single set > of code that gets customized via a single change of an API key. This > means that all of the applications have the same activities, same > behaviors, but different icons, package names, and application names > depending on the client I am building for. > > Unfortunately, I haven't figured out a clean way to do this. Because > the package name is what the Android Marketplace uses, I've been > changing it to com.nilobject.productname.clientname. However, this > changes the package for all of the activities to no longer be in the > package of the application, since they live in > "com.nilobject.productname." Additionally, the autogenerated "R" > moves, so all of the references to R in com.nilobject.productname > break. > > Has anyone else dealt with this problem? I'm using Eclipse for > development. Should I just refactor the activities with each build to > be in the same package? Is there a system for this that I don't know > about? > > Thanks for any ideas and help! -- 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
