| Age | Commit message (Collapse) | Author |
|---|
|
Can be annotation processor or plugin specific flags that might
not be supported by javac.
|
|
|
|
Add new option, flycheck-android-java-variant, if a matching variant
is found the matching configuration is used. If no matching variant
is found the first one is used - same as if you had not set a variant.
Variant is case-sensitive.
|
|
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.
|
|
|
|
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
|
|
|
|
|
|
|
|
|
