After 10 years in Mobile, I’ve moved to Autonomous Vehicles DevOps @ Lyft and now I need to fill a lot of knowledge gaps. Join me on this journey!
Please leave the comments with the best articles|videos you’ve seen. And learn from others.
Bazel
#Bazel #CI #BazelCon 2019: https://youtu.be/BYg3fDFrTz8
#Bazel #Testing #BazelCon2019: https://youtu.be/9Dk7mtIm7_A
Spinnaker
#Spinnaker #CI #CD #Next2017 https://youtu.be/05EZx3MBHSY
#Spinnaker #DevOps #Netflix https://youtu.be/UTKIT6STSVM
Immutable Infrastructure
#ImmutableInfra #HashiCorp https://youtu.be/II4PFe9BbmE
Bonus
#ArtOfCode https://youtu.be/6avJHaC3C2U
As you could notice in my previous article, using Java 11 VM’s is pretty straight forward with sample apps. But what we should do when it does not work?
One of the possible setups where Java11 failed is Android Kotlin projects with KAPT and Dagger2. Let’s see how we can emulate this setup and fix it.
Extending our Sample App
Simple Dagger Component
Adding Component like this in your project — already causing an issue.
What happened here?
Well, Logs are clearly showing — Java is to blame. But the real problem here is KAPT.
Let’s see how we can deal with it, and there are 2 options…
Java 8 was a long-awaited feature in the Android community. Finally, we got almost full support of language features. Unfortunately, newer versions of Java on Android remains just a dream.
Java updates are hard to adapt for Android, and this is one of the reasons why Google is promoting Kotlin as the Main language for application development. Despite disadvantages such as slow compilation times and slow code editing Kotlin getting more and more popular, especially in New Projects.
In this series of articles, I’ll try to demonstrate how we can finally make use of all new Java11 Virtual Machines to compile Android Projects with Kotlin. …
About
