WALA/com.ibm.wala.shrike
Ben Liblit 89860b53bb Let Buildship create new settings files when importing
These settings files currently are generated with an initial timestamp
comment line, which is not something we'd want to track in version
control.  Fortunately, the contents of these files are entirely
mundane, so there should be no problem with having Buildship generate
them anew each time a developer imports WALA into Eclipse as an
existing Gradle project.
2018-04-18 11:29:25 -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
releng File that maps plugin version to contained src file versions. 2007-12-08 20:55:46 +00:00
src/com/ibm/wala Revert "Build WALA using Gradle instead of Maven" (#298) 2018-04-18 12:15:56 -04:00
build.gradle Have Buildship add Eclipse plugin (PDE) nature to some subprojects 2018-04-18 11:29:25 -05:00
build.properties Revert "Build WALA using Gradle instead of Maven" (#298) 2018-04-18 12:15:56 -04:00
cg.jardesc 1) changes for mobile 2015-05-25 19:00:51 -04:00
codescrape.jardesc 1) changes for mobile 2015-05-25 19:00:51 -04:00
exportPlugin.xml Add stub DOCTYPE declarations for various hand-authored XML files 2016-11-28 14:55:34 -06:00
javaCompiler...args mv stuff to trunk 2006-11-22 17:45:24 +00:00
manifest.cg 1) changes for mobile 2015-05-25 19:00:51 -04:00
manifest.codescrape 1) changes for mobile 2015-05-25 19:00:51 -04:00
mvncentral.xml Revert "Build WALA using Gradle instead of Maven" (#298) 2018-04-18 12:15:56 -04:00
plugin.properties complete conversion to Unix line endings 2012-09-04 16:05:49 -07:00
pom.xml Revert "Build WALA using Gradle instead of Maven" (#298) 2018-04-18 12:15:56 -04:00