WALA/com.ibm.wala.cast.js.test
Ben Liblit 858148e91b Reorganize how we deal with shared JavaScript test examples
When IntelliJ IDEA imports WALA's Gradle configuration, it creates
what is calls a "module" for each sourceSet of each Gradle subproject.
In so doing, it automatically picks up the source and resource
directories used by each of these sourceSets.  Unfortunately, IntelliJ
IDEA does not allow multiple modules to share a single root directory
as their source or resource directories, and that's exactly what was
going on with the "example-src" subdirectory under
"com.ibm.wala.cast.js.test.data".

This revised Gradle configuration still has is copying the necessary
"example-src" resources to the appropriate locations for use as test
resources.  But IntelliJ IDEA no longer treats "example-src" as a root
directory for resources in the automatically-generated modules.  So
now we get along nicer with IntelliJ IDEA while keeping everything
working with Gradle as well.
2018-07-11 16:13:05 -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 Bump version to 1.5.0-SNAPSHOT before merging with WALA master 2018-04-18 11:29:29 -05:00
OSGI-INF/l10n Externalize bundle names and vendors 2017-06-07 17:42:11 +02:00
harness-src/com/ibm/wala/cast/js/test move code for sharing between javascript and python 2018-04-30 13:33:48 -04:00
build.gradle Reorganize how we deal with shared JavaScript test examples 2018-07-11 16:13:05 -05:00
build.properties Externalize bundle names and vendors 2017-06-07 17:42:11 +02:00
pom.xml Require JUnit 4.12 instead of 4.11 2018-05-21 17:27:54 -05:00