Personally I'd use a version control system with branches to do this. And keep it in one project.
Doing it with branches you could easily merge changes that go in both versions, and just do a refresh in eclipse when doing development on the other version. On Mar 11, 10:51 pm, "Matt (preinvent)" <[email protected]> wrote: > I have a free app out there and am going to write a pro version with > some extra functionality that I'll charge for. > > The plan is to use the same code for both apps, although I need > different Eclipse projects to use different manfiest files. The > obvious way is to have all my code in a shared library which the free > and pro projects reference. > > Is there a recommended way of doing this? -- 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
