Also the Froyo aapt has an option to change the manifest package name at build time. This new aapt option should work with any version of the platform.
On Wed, Jun 2, 2010 at 4:41 AM, Mark Murphy <[email protected]> wrote: > blcooley wrote: > > 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? > > Look at the new "library project" facility added in the latest edition > of the Android development tools, as it may fit your needs. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > Android Consulting: http://commonsware.com/consulting > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
