Add android example app to farm initial issues and for e2e testing.

[hsyed]

Note:

• The android rules only recognise java_import See this issue in the old rule repo and upstream issue. java_import drops kotlin inline code but will be addressed by this.

Purpose:

• End-to-End Tests for interaction with the native android rules.
• Test app for validating the intellij and android studio plugins.
• Farming issues with the rules that need to be made for android. This include discovering new macros that might be needed.

Must:

• Exercise all appropriate rule orchestrations between the kt_jvm_* and the android rules.
• Stay within the android SDK as much as possible, we don't add the entire universe as external (maven) deps -- if we need a lot of external deps we should consider bazel-deps or spotify/bazel-tools.
• Use an external version of the android SDK --e.g., http_archive.
• Wire up the android SDK in a way so that the recommended SDK version is used with the recommended Bazel version for CI testing -- in other words build flags, config settings and select.
• (in addition to android studio) be compilable and navigable in intellij CE or ultimate, at least the Kotlin code.
• Work without an IDE (this one might be obvious, but for all I know there is coupling with android studio).

[hsyed]

@davidstanke I'll assign this to you since I don't do any android development internally. I doubt much nitty gritty rule development work needs to occur, we might end up with some android specific macros.

@cgruber are you interested in taking a stab at this one ? If we do need to add android specific macros all design questions will probably go to you.

[cgruber]

I'm in no position to put the time into this one, though part of me would love to. Let me see how I'm doing next week.

…

On Tue, 13 Feb 2018 at 16:47 Hassan Syed ***@***.***> wrote: @davidstanke <https://github.com/davidstanke> I'll assign this to you since I don't do any android development internally. I doubt much nitty gritty rule development work needs to occur, we might end up with some android specific macros. @cgruber <https://github.com/cgruber> are you interested in taking a stab at this one ? If we do need to add android specific macros all design questions will probably go to you. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAUN4sWLiu17VnPa_VBySKyyZ4ytHfKpks5tUi0cgaJpZM4SEhj-> .

[hsyed]

Android is now supported(#117 ), it was easier then I anticipated. I need a proper sample project to verify everything is working as intended.