Moving Baku debug features to V-Android
This pulls in ReactiveX, RetroLambda, and Lombok:
* ReactiveX adds the Observable class which represents an asynchronous
sequence of productions. VAndroidContext was using this for error
reporting and blessings management. For now, I am omitting the
blessings management since it is not clear abstracting
BlessingsManager in that way is what we want to do in the long run,
but ReactiveX adds significant value in deduping error reporting, and
is likely to be used for Syncbase watch in the future, as it adds
powerful features to the V23 Java InputChannel.
* RetroLambda allows the use of Java 8 features in Android. This does
not require the use of Java 8 features by library consumers, and
Android N will support a subset of Java 8 out of the box.
* Lombok reduces boilerplate and is a compile-time-only
dependency. Proper integration does warrant additional work to
integrate Delombok for Javadoc and potentially source generation, but
that is not necessary at this time and probably warrants a few
third-party library modifications to do well.
ReactiveX is the primary transitive dependency to think about;
RetroLambda and Lombok only make working on the library itself easier
and should have little impact on consumers.
Change-Id: I2c30fb0876bdf07b6724321877abb438aaf9f5d3
32 files changed
