You could also use a scheme like preprocesser directives in C. Define a static final bool FREE and do a lot of if(FREE) to check which build you are on. The downside is you still need to do manual work.
But the best approach is using ant for this, at least I think this stuff is possible using ant. Using the static final method in combination with different files you use from the ant script. On Jun 4, 7:36 pm, Robert Green <[email protected]> wrote: > I did it in eclipse and it didn't take me over 30 minutes to get > everything copied. I'm pretty sure that I copied the entire project > directly, renamed it, then moved all classes to the new package, > updated the Manifest and that was it. > > On Jun 4, 12:54 am, chrispix <[email protected]> wrote: > > > > > We have a paid app in the market place, we would like to release a > > demo of the paid app. I was hoping we could just recompile w/ the same > > package name, but apparently that does not work. > > > I have tried manually changing package name etc, but it is a chore, > > and it seems that several things that automatically happen in eclipse > > cause more harm than good when renaming the package name. > > > Which brings me to my next question. If having a new package name is > > the only way to accomplish this. Is there an easy way to fork the paid > > app, where keeping the changes synchronized is easier? Some kind of > > Source Control? > > > Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
