Can I use retrolambda after end of 2019?

[BearCola]

Whenever enter into Android Studio, I got follow warning message

WARNING: API 'variant.getJavaCompile()' is obsolete and has been replaced with 'variant.getJavaCompileProvider()'.
It will be removed at the end of 2019.
For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
REASON: It is currently called from the following trace:
java.lang.Thread.getStackTrace(Thread.java:1556)
com.android.build.gradle.internal.errors.DeprecationReporterImpl.reportDeprecatedApi(DeprecationReporterImpl.kt:79)
com.android.build.gradle.internal.api.BaseVariantImpl.getJavaCompile(BaseVariantImpl.java:423)
com.android.build.gradle.internal.api.TestVariantImpl_Decorated.getJavaCompile(null:-1)
me.tatarka.RetrolambdaPluginAndroid.configureCompileJavaTask(RetrolambdaPluginAndroid.groovy:106)
me.tatarka.RetrolambdaPluginAndroid.access$3(RetrolambdaPluginAndroid.groovy:-1)
me.tatarka.RetrolambdaPluginAndroid$_apply_closure2.doCall(RetrolambdaPluginAndroid.groovy:53)

This means getJavaCompile will removed but retrolambda use this.
Is there any release plan for this?

[evant]

PR welcome. Am curious why you aren't using the built-in desugaring on Android though.

[BearCola]

@evant We develop sdk for game company. But usually game company doesn't add below option.
this occurs error in game.
But when I use retrolambda there is no probrem :)

compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}