| Age | Commit message (Collapse) | Author |
|
|
|
Can be annotation processor or plugin specific flags that might
not be supported by javac.
|
|
|
|
|
|
Two new options:
flycheck-android-java-variant: Select variant to check instead of
picking the first which is the default
flycheck-android-java-skip-gen: Skip running generate*Sources before
check
|
|
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.
|
|
|
|
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
|
|
|
|
|
|
|
|
Bump emacs version to 0.3.4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 420f42cda4434bacf587b5082a25cce225502d26.
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|