DASCA/WALA
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Fork of the T.J. Watson Libraries for Analysis used by DASCA.
5,803 Commits 8 Branches 13 Tags 81 MiB
Java 94.4%
JavaScript 4.3%
HTML 0.5%
C++ 0.4%
Gradle 0.3%
8529c10491
Go to file
Ben Liblit 8529c10491 Use Gradle to create selected Eclipse metadata before Maven builds 
The Eclipse metadata files created in this way are not identical to
those that Buildship would create when importing into Eclipse.  The
tests in com.ibm.wala.cast.java.test.JDTJava15IRTests and
com.ibm.wala.cast.java.test.JDTJavaIRTests seem to pass using either
the Gradle-generated or the Buildship-generated versions.

As an aside, if you generate these files using Gradle first and *then*
import using Buildship, you end up with metadata that is identical to
what you would have had if you'd only imported with
Buildship.  (There's one irrelevant difference in an unimportant
"<comment>" element.)  So Maven's tests should run fine under any
wacky mix of Gradle- and Buildship-generated Eclipse metadata files.

That being said, I recommend not mixing build systems.  WALA can be
built using either Maven, Gradle, or Eclipse+Buildship, but you're
probably better off only using one of these in any given build tree.
A mixed tree *should* probably work, but I haven't tested it
thoroughly, and consider better to avoid doing.

Incidentally, if there are other Maven-preparation steps that we'd
like Gradle to automate for us, that can now be done easily by
creating more "prepareMavenBuild" Gradle tasks in other subprojects
and adding the appropriate dependencies.  For example, it would be
trivial to use this to automate downloading "/tmp/DroidBench",
installing the Android SDK, etc.
2018-04-18 11:29:29 -05:00
buildSrc Improve build caching by reducing path sensitivity where appropriate 2018-04-18 11:29:29 -05:00
com.ibm.wala_feature Let Buildship create new settings files when importing 2018-04-18 11:29:25 -05:00
com.ibm.wala-repository Let Buildship create new settings files when importing 2018-04-18 11:29:25 -05:00
com.ibm.wala.cast Simplify how we refer to the outputs of certain tasks 2018-04-18 11:29:29 -05:00
com.ibm.wala.cast.java Tweak output dirs to match what Buildship puts into ".classpath" 2018-04-18 11:29:25 -05:00
com.ibm.wala.cast.java.ecj Find Eclipse jars using local Maven mirror of Eclipse P2 repository 2018-04-18 11:29:28 -05:00
com.ibm.wala.cast.java.test Add some Eclipse dependencies needed only when running tests 2018-04-18 11:29:28 -05:00
com.ibm.wala.cast.java.test.data Use Gradle to create selected Eclipse metadata before Maven builds 2018-04-18 11:29:29 -05:00
com.ibm.wala.cast.js Restore old manifests in hope of fixing Maven regressions 2018-04-18 11:29:29 -05:00
com.ibm.wala.cast.js.html.nu_validator Ignore some transient files that appear during testing 2018-04-18 11:29:27 -05:00
com.ibm.wala.cast.js.nodejs more work on file names 2018-04-18 11:29:29 -05:00
com.ibm.wala.cast.js.nodejs.test Exclude a test that has started failing due to running out of memory 2018-04-18 11:29:29 -05:00
com.ibm.wala.cast.js.rhino Restore old manifests in hope of fixing Maven regressions 2018-04-18 11:29:29 -05:00
com.ibm.wala.cast.js.rhino.test Update Eclipse JUnit test launchers for use with Buildship 2018-04-18 11:29:27 -05:00
com.ibm.wala.cast.js.test Update Eclipse JUnit test launchers for use with Buildship 2018-04-18 11:29:27 -05:00
com.ibm.wala.cast.js.test.data Simplify how we refer to the outputs of certain tasks 2018-04-18 11:29:29 -05:00
com.ibm.wala.cast.test Don't try to exhaustively anticipate all generated header names 2018-04-18 11:29:29 -05:00
com.ibm.wala.core Fix various warnings produced by "./gradlew javadoc" 2018-04-18 11:29:27 -05:00
com.ibm.wala.core.testdata Simplify how we refer to the outputs of certain tasks 2018-04-18 11:29:29 -05:00
com.ibm.wala.core.tests Don't put fixed-name, writable files into "java.io.tmpdir" 2018-04-18 11:29:29 -05:00
com.ibm.wala.dalvik Simplify how we refer to the outputs of certain tasks 2018-04-18 11:29:29 -05:00
com.ibm.wala.dalvik.test Simplify how we refer to the outputs of certain tasks 2018-04-18 11:29:29 -05:00
com.ibm.wala.ide Find Eclipse jars using local Maven mirror of Eclipse P2 repository 2018-04-18 11:29:28 -05:00
com.ibm.wala.ide_feature Let Buildship create new settings files when importing 2018-04-18 11:29:25 -05:00
com.ibm.wala.ide.jdt Find Eclipse jars using local Maven mirror of Eclipse P2 repository 2018-04-18 11:29:28 -05:00
com.ibm.wala.ide.jdt.test Add some Eclipse dependencies needed only when running tests 2018-04-18 11:29:28 -05:00
com.ibm.wala.ide.jsdt Restore old manifests in hope of fixing Maven regressions 2018-04-18 11:29:29 -05:00
com.ibm.wala.ide.jsdt.tests Add a resource directory containing a zip archive used for testing 2018-04-18 11:29:28 -05:00
com.ibm.wala.ide.tests Restore old manifests in hope of fixing Maven regressions 2018-04-18 11:29:29 -05:00
com.ibm.wala.scandroid Let Buildship create new settings files when importing 2018-04-18 11:29:25 -05:00
com.ibm.wala.shrike Don't put fixed-name, writable files into "java.io.tmpdir" 2018-04-18 11:29:29 -05:00
com.ibm.wala.tests_feature Let Buildship create new settings files when importing 2018-04-18 11:29:25 -05:00
com.ibm.wala.tests.ide_feature Let Buildship create new settings files when importing 2018-04-18 11:29:25 -05:00
com.ibm.wala.util Fix various warnings produced by "./gradlew javadoc" 2018-04-18 11:29:27 -05:00
gradle/wrapper Update to Gradle 4.6 2018-04-18 11:29:28 -05:00
targets Revert "Build WALA using Gradle instead of Maven" (#298) 2018-04-18 12:15:56 -04:00
travis Use Gradle to create selected Eclipse metadata before Maven builds 2018-04-18 11:29:29 -05:00
.dir-locals.el Many improvements to Gradle build support, including within Eclipse 2018-04-18 11:29:24 -05:00
.gitignore We only expect ".gradle" directories in two specific places 2018-04-18 11:29:28 -05:00
.travis.yml Bail out if any Travis CI testing commands fail 2018-04-18 11:29:29 -05:00
After Importing WALA Into Eclipse.launch Generalize post-import Eclipse run configuration for more fixups 2018-04-18 11:29:28 -05:00
appveyor.yml.disabled disable appveyor for now 2017-04-13 22:06:35 -07:00
build-maven-jars.py make Maven Central files for wala.dalvik and wala.scandroid (#158) 2017-03-25 13:20:34 -07:00
build.gradle Allow parallel testing within each subproject 2018-04-18 11:29:29 -05:00
change-version.py script to change version numbers consistently across files 2015-05-29 12:19:18 -07:00
dependent-projects-trigger.sh build ML projects 2018-04-13 09:11:57 -04:00
gradle.properties Enable both parallel builds and build output caching by default 2018-04-18 11:29:29 -05:00
gradlew Support the gradlew build 2018-04-18 11:29:24 -05:00
gradlew.bat Support the gradlew build 2018-04-18 11:29:24 -05:00
LICENSE Create LICENSE 2018-03-08 09:08:53 -05:00
pom.xml Revert "Build WALA using Gradle instead of Maven" (#298) 2018-04-18 12:15:56 -04:00
README-Gradle.md Use Gradle to create selected Eclipse metadata before Maven builds 2018-04-18 11:29:29 -05:00
README.md Add a new README with Gradle-specific instructions and tips 2018-04-18 11:29:28 -05:00
revert-launchers.sh Generalize post-import Eclipse run configuration for more fixups 2018-04-18 11:29:28 -05:00
settings.gradle Set name and version to help Gradle composite-build substitutions 2018-04-18 11:29:27 -05:00
upload-javascript.sh quiet 2017-08-03 21:11:33 +00:00

README.md

WALA Build Status

This is the main source repository for WALA. For more details on WALA, see the WALA home page and WALA Javadoc.

Note: historically, WALA has used Maven as its build system. However, this WALA branch can also use Gradle as an alternative to Maven. See the Gradle-specific README for more instructions and helpful tips.