Remove any special casing around the former android backend.
Review Request #3531 - Created March 2, 2016 and submitted
|gmalmquist, jsirois, patricklaw, stuhood, zundel|
This has to land along with the move to contrib
but I broke it up to make it easier to review.
This commit removes all the special casing that accrued
over the years as a consequence of having Android as a
separate backend. It also puts together some new
special casing that allows the android tests to still
be skipped in circumstances where that is needed.
This adds a flag to skip the new android contrib package
when running CIs. Because OSX does not have container
based CI it would have to download and bootstrap the SDK
each run. That is not feasible for multiple reasons.
During the release of the package, it will not run the actual
Android tests because the releaser will usually not have the
SDK installed on their machine. This just checks to see if the
various goals are installed.
CI.sh and release.sh passed.
A travis run with the code from both CR 3530 and 3531 is away at:
Both of those commits will have to land at the same time.
So this is not quite out of the woods yet - now that this is in contrib it runs the android tests by default. Those tests are designed to not run if ANDROID_HOME is not set - but we set it in ivysettings.xml. So either I need to hack a '--skip-android' into the CONTRIB tests or (even better) download the sdk into the travis container. John and I are planning to talk about that last idea sometime this week.
Add a 'skip android' flag back to the CI and get all tests to pass (I believe - CR in flight)
Revision 2 (+45 -3)
This is all green - feel free to rubber stamp the two dependent CRs 3530 and 3531.
The upshot is that gets the Android backend all green and all the examples to build. It then moves
the entire Android backend out of backend and into its own contrib module. The -a flag on any
ci scripts will still skip the Android backend as before.