From 38167e774934b643338f94201b16a922d80bc448 Mon Sep 17 00:00:00 2001
From: Joel Klinghed <the_jk@opera.com>
Date: Tue, 5 Dec 2017 13:30:14 +0100
Subject: Stop hardcoding generateDebugSources

Instead we write a list of generate tasks to output of flycheckAndroidJava
task and let the pyhton script run them

Reason to do it like this is that when the FlycheckAndroidJava task
is created it's to early to get the list of buildtypes or flavors
from the extensions.
---
 src/main/groovy/FlycheckAndroidJavaTask.groovy | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

(limited to 'src/main/groovy/FlycheckAndroidJavaTask.groovy')

diff --git a/src/main/groovy/FlycheckAndroidJavaTask.groovy b/src/main/groovy/FlycheckAndroidJavaTask.groovy
index d7ce2da..633c445 100644
--- a/src/main/groovy/FlycheckAndroidJavaTask.groovy
+++ b/src/main/groovy/FlycheckAndroidJavaTask.groovy
@@ -6,7 +6,6 @@ import org.gradle.api.tasks.compile.JavaCompile
 
 class FlycheckAndroidJavaTask extends DefaultTask {
     FlycheckAndroidJavaTask() {
-        dependsOn 'generateDebugSources'
     }
 
     @TaskAction
@@ -50,5 +49,13 @@ class FlycheckAndroidJavaTask extends DefaultTask {
                 println 'output=' + compile.destinationDir
             }
         }
+
+        def name = 'generate'
+        name += variants.first().capitalize() + 'Sources'
+        def generate = project.tasks.findByName(name)
+        if (generate != null) {
+            println '!!!'
+            println generate.path
+        }
     }
 }
-- 
cgit v1.2.3-70-g09d2