Open stephanenicolas opened 7 years ago
Hm, shouldn't this be the job of the transform api to implement?
Sorry, I actually realized that the new android plugin version 3.0 allows to remove retro lambda. So, we don't need this feature anymore from retro lambda.
But in case you want to implement it, it's on your side if you create a new type of task.
2017-08-09 13:31 GMT-07:00 Evan Tatarka notifications@github.com:
Hm, shouldn't this be the job of the transform api to implement?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/evant/gradle-retrolambda/issues/258#issuecomment-321373056, or mute the thread https://github.com/notifications/unsubscribe-auth/ABv33Wz3bU-8hRDJtNZWZWiOZISld8Qeks5sWhc9gaJpZM4Oyecg .
Yeah, 3.0 is going to be the last version I plan on supporting. Unfortunately by using the transform api I don't have control of the task itself. I might look into it for the plain java version though.
Even though we are probably gonna stop using retro lambda, I would like to take some time to thank you for bringing this to android. Thanks a lot for all your work !
2017-08-09 14:15 GMT-07:00 Evan Tatarka notifications@github.com:
Yeah, 3.0 is going to be the last version I plan on supporting. Unfortunately by using the transform api I don't have control of the task itself. I might look into it for the plain java version though.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/evant/gradle-retrolambda/issues/258#issuecomment-321383627, or mute the thread https://github.com/notifications/unsubscribe-auth/ABv33d1FqzOgTr10wEK27pgpKIW5hU25ks5sWiF-gaJpZM4Oyecg .
It looks like the retro lambda tasks are not cacheable by gradle: https://docs.gradle.org/3.5/userguide/build_cache.html