| Age | Commit message (Collapse) | Author |
|---|
|
Not all subprojects have all the variants that the app project has.
|
|
|
|
Useful for custom checks
|
|
For large projects running generate*Sources can incur a heavy cost
|
|
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.
|
|
|
|
|
|
This means you have to do real build less often as you change
the API of different classes. However, it instead means that we can
end up with outdated class files if you check out new code and
build without revisiting the buffer in Emacs. So, to work around
that, we check that no class file is older than the ones in
the real output dir. But to keep everything fast, this is launched
in a background process
|
|
First, a file that only exists as a buffer, not even saved yet:
* Pick the first Java target found, it will probably work
* Complain if not found instead of silently pretend the file is valid
Second, a file that was added after the last gradle run so
cache doesn't contain it:
* If no fitting target was found, and the file exist and we used
cached data, force a new gradle run
|
|
|
|
|
|
|
|
|
