Ben Liblit 4840966807 Don't try to exhaustively anticipate all generated header names ... When JNI headers for a given class, each nested class will end up with its own additional header. But I don't want to try to parse nested class details out of the Java source files just so we can determine exactly which headers will be created. Instead, simply treat the entire header destination directory as the output of this task.		2018-04-18 11:29:29 -05:00
..
.launchConfigurations	Update Eclipse JUnit test launchers for use with Buildship	2018-04-18 11:29:27 -05:00
.settings	Let Buildship create new settings files when importing	2018-04-18 11:29:25 -05:00
META-INF	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
OSGI-INF/l10n	Externalize bundle names and vendors	2017-06-07 17:42:11 +02:00
harness-src	native config cleanup	2018-01-20 17:40:10 +00:00
build.gradle	Don't try to exhaustively anticipate all generated header names	2018-04-18 11:29:29 -05:00
build.properties	Simplify inclusion of "OSGI-INF" and the only file it contains	2018-04-18 11:29:25 -05:00
excluded-tests.txt	exclude abstract test	2007-11-16 02:04:39 +00:00
pom.xml	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00