I've been holding off on replying to this only because I haven't fully collected my thoughts. I hope to write up my recommendations for build approaches, especially for free/paid apps, before really wrapping my mind around it.
But since that's taking me a while, I thought I should chime in, "yes, I'm interested". Quite. But one thought is that making this be a command may not be the best approach for integration into build systems. I'm thinking that packaging it as an ant macro in an antlib may be a better approach, with the underlying technology being a .zip file with the various pieces. Then, if you feel the need for a command, you could create an ant script, and simple shell scripts to invoke it. This would leverage Ant's facilities (.zip files, file operations, xslt to update the manifest, etc), give you platform independence, and not require any software installation other than the antlib, since people already need ant (even if they don't know it). It's not that I'm a huge fan of ant. But it's adequate, and already a part of the tool mix. And I see the primary endpoint being good integration with building, and ant is a key part of that for most of us. It looks like this should mostly integrate cleanly with the build approach I'm about to blog about. My approach, for production builds, produces pristine clones of your hierarchy, so injecting into this won't interfere with revision control systems or builds. However, there are issues to work out about integration with Eclipse. Or alternatively, we could inject into a project, and then check it in. The problem here is that managing upgrading to a new revision of a library becomes more problematic, as you need to consider unwinding changes to the manifest, removing files no longer needed, etc. Overall, I think it's cleaner to consider injection to be a build step, rather than a project configuration step. You also need to consider how to avoid and/or handle file name conflicts. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using "remove me" as the subject.
