Friday, March 22, 2013


While the move to having android testing in the same
project via the next ADT and tools major revision solves some problems there is still an underlying set of problems. What do you do when the android lib uses a different build system than your project as far as workflow to avoid just copying files over all the time.

The problem gets more complicated as the IDE eclipse only allows one src per project, etc. But if we do some simple changes to our build scripts and workflow it can work. How?

It starts with a very simple gem of trick or hack:

OurAndrdoid LibProjectModified/

See what I did there? This trick establishes a way to put in a project build overlay that plugs into the parent project build without forcing us to use maven and it allows for the updating of the android lib from a 3rd party via the upstream reference.

Yes, when Google switches to using Gradle you will still have to change whatever default gradle build script Google comes up with but thishack the changes will be minimal.