| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2017-12-05 | Stop hardcoding generateDebugSources | Joel Klinghed | |
| 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. | |||
| 2017-12-05 | Add support for non-experimental gradle plugin | Joel Klinghed | |
| 2017-12-05 | Support gradle-experimental-0.11.0 | Joel Klinghed | |
| Problem with the new gradle-experimental is that tasks are only created if needed, so searching for a generateDebugSources or compile*DebugJavaWithJavac is pointless as unless there is a dependency on them the tasks do not exist Only create the FlycheckAndroidJavaTask for projects that implement either an Android App module or Android Library module so that we can assume there will always be a generateDebugSources task. And use buildTypes and flavors to figure out what compile task names there should be and reference them directly | |||
| 2017-09-20 | Support projects using productFlavors | Joel Klinghed | |
| 2017-03-23 | Add test target as well | Joel Klinghed | |
| 2017-01-24 | Bump gradle plugin 0.3.2 and add support for initscript plugin | Joel Klinghed | |
| 2017-01-10 | All the rest | Joel Klinghed | |
