Ben Liblit 4dc1e41529 Tell Eclipse to ignore some questionable manifest contents ... These manifest files are here for use by the Maven build, but Eclipse is now using Gradle (via Buildship). So the manifests as seen by Eclipse do not entirely make sense. I'm hesitant to change the manifests directly, since presumably they were correct for Maven and still are. Perhaps some day we'll be using Gradle to generate manifests. Until that day comes, we're better off leaving the manifests as they are and just suppressing Eclipse's warnings instead.		2018-04-18 11:29:29 -05:00
..
.settings	Tell Eclipse to ignore some questionable manifest contents	2018-04-18 11:29:29 -05:00
META-INF	Restore old manifests in hope of fixing Maven regressions	2018-04-18 11:29:29 -05:00
OSGI-INF/l10n	Externalize bundle names and vendors	2017-06-07 17:42:11 +02:00
data	Initial contribution of core script analysis code	2007-02-02 17:17:13 +00:00
source	Clean up questionable memory management during string construction	2018-04-18 11:29:29 -05:00
build.gradle	Incremental improvements to Windows JDK library configuration	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
mvncentral.xml	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00
pom.xml	Revert "Build WALA using Gradle instead of Maven" (#298)	2018-04-18 12:15:56 -04:00