{"id":34349921,"url":"https://github.com/wala/wala","last_synced_at":"2026-04-04T13:00:59.426Z","repository":{"id":2931561,"uuid":"3943003","full_name":"wala/WALA","owner":"wala","description":"T.J. Watson Libraries for Analysis, with front ends for Java, Android, and JavaScript, and many common static program analyses.","archived":false,"fork":false,"pushed_at":"2026-04-01T20:37:35.000Z","size":62736,"stargazers_count":839,"open_issues_count":149,"forks_count":240,"subscribers_count":25,"default_branch":"master","last_synced_at":"2026-04-02T07:59:31.572Z","etag":null,"topics":["android","callgraph","dataflow-analysis","java","javascript","pointer-analysis","program-analysis","slicing","static-analysis","static-code-analysis"],"latest_commit_sha":null,"homepage":"http://github.com/wala/WALA","language":"Java","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"epl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/wala.png","metadata":{"files":{"readme":"README-Gradle.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2012-04-05T18:57:03.000Z","updated_at":"2026-04-01T20:37:39.000Z","dependencies_parsed_at":"2026-01-30T01:03:56.721Z","dependency_job_id":null,"html_url":"https://github.com/wala/WALA","commit_stats":{"total_commits":6914,"total_committers":84,"mean_commits":82.30952380952381,"dds":0.7078391669077235,"last_synced_commit":"2f79c10f1188d4b2ef3904e2b5c39c0beebd9e5f"},"previous_names":[],"tags_count":34,"template":false,"template_full_name":null,"purl":"pkg:github/wala/WALA","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/wala%2FWALA","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/wala%2FWALA/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/wala%2FWALA/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/wala%2FWALA/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/wala","download_url":"https://codeload.github.com/wala/WALA/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/wala%2FWALA/sbom","scorecard":{"id":688015,"data":{"date":"2025-08-04","repo":{"name":"github.com/wala/WALA","commit":"70ae7e0c5b13d55b3d901ec4f9508d92e41766e7"},"scorecard":{"version":"v5.2.1-28-gc1d103a9","commit":"c1d103a9bb9f635ec7260bf9aa0699466fa4be0e"},"score":5.4,"checks":[{"name":"Code-Review","score":9,"reason":"Found 28/30 approved changesets -- score normalized to 9","details":null,"documentation":{"short":"Determines if the project requires human code review before pull requests (aka merge requests) are merged.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#code-review"}},{"name":"Maintained","score":10,"reason":"30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10","details":null,"documentation":{"short":"Determines if the project is \"actively maintained\".","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#maintained"}},{"name":"Token-Permissions","score":0,"reason":"detected GitHub workflow tokens with excessive permissions","details":["Warn: jobLevel 'checks' permission set to 'write': .github/workflows/publish-test-results.yml:15","Info: jobLevel 'contents' permission set to 'read': .github/workflows/publish-test-results.yml:17","Info: jobLevel 'issues' permission set to 'read': .github/workflows/publish-test-results.yml:18","Info: jobLevel 'actions' permission set to 'read': .github/workflows/publish-test-results.yml:19","Warn: no topLevel permission defined: .github/workflows/continuous-integration.yml:1","Info: found token with 'none' permissions: .github/workflows/publish-test-results.yml:1"],"documentation":{"short":"Determines if the project's workflows follow the principle of least privilege.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#token-permissions"}},{"name":"Dangerous-Workflow","score":10,"reason":"no dangerous workflow patterns detected","details":null,"documentation":{"short":"Determines if the project's GitHub Action workflows avoid dangerous patterns.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#dangerous-workflow"}},{"name":"CII-Best-Practices","score":0,"reason":"no effort to earn an OpenSSF best practices badge detected","details":null,"documentation":{"short":"Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#cii-best-practices"}},{"name":"Security-Policy","score":0,"reason":"security policy file not detected","details":["Warn: no security policy file detected","Warn: no security file to analyze","Warn: no security file to analyze","Warn: no security file to analyze"],"documentation":{"short":"Determines if the project has published a security policy.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#security-policy"}},{"name":"Vulnerabilities","score":10,"reason":"0 existing vulnerabilities detected","details":null,"documentation":{"short":"Determines if the project has open, known unfixed vulnerabilities.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#vulnerabilities"}},{"name":"License","score":10,"reason":"license file detected","details":["Info: project has a license file: LICENSE:0","Info: FSF or OSI recognized license: Eclipse Public License 2.0: LICENSE:0"],"documentation":{"short":"Determines if the project has defined a license.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#license"}},{"name":"Binary-Artifacts","score":3,"reason":"binaries present in source code","details":["Warn: binary detected: core/classes/CodeDeleted.class:1","Warn: binary detected: core/classes/DupFieldName.class:1","Warn: binary detected: core/classes/MissingMethodRef.class:1","Warn: binary detected: core/classes/missingmetadata/MissingClassRef.class:1","Warn: binary detected: core/classes/missingsuper/MissingSuper.class:1","Warn: binary detected: core/ocaml/hello_hash.jar:1","Warn: binary detected: gradle/wrapper/gradle-wrapper.jar:1"],"documentation":{"short":"Determines if the project has generated executable (binary) artifacts in the source repository.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#binary-artifacts"}},{"name":"Signed-Releases","score":-1,"reason":"no releases found","details":null,"documentation":{"short":"Determines if the project cryptographically signs release artifacts.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#signed-releases"}},{"name":"Branch-Protection","score":-1,"reason":"internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration","details":null,"documentation":{"short":"Determines if the default and release branches are protected with GitHub's branch protection settings.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#branch-protection"}},{"name":"Pinned-Dependencies","score":1,"reason":"dependency not pinned by hash detected -- score normalized to 1","details":["Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/continuous-integration.yml:41: update your workflow using https://app.stepsecurity.io/secureworkflow/wala/WALA/continuous-integration.yml/master?enable=pin","Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/continuous-integration.yml:43: update your workflow using https://app.stepsecurity.io/secureworkflow/wala/WALA/continuous-integration.yml/master?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/continuous-integration.yml:48: update your workflow using https://app.stepsecurity.io/secureworkflow/wala/WALA/continuous-integration.yml/master?enable=pin","Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/continuous-integration.yml:63: update your workflow using https://app.stepsecurity.io/secureworkflow/wala/WALA/continuous-integration.yml/master?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/continuous-integration.yml:72: update your workflow using https://app.stepsecurity.io/secureworkflow/wala/WALA/continuous-integration.yml/master?enable=pin","Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/continuous-integration.yml:82: update your workflow using https://app.stepsecurity.io/secureworkflow/wala/WALA/continuous-integration.yml/master?enable=pin","Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/continuous-integration.yml:95: update your workflow using https://app.stepsecurity.io/secureworkflow/wala/WALA/continuous-integration.yml/master?enable=pin","Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/continuous-integration.yml:97: update your workflow using https://app.stepsecurity.io/secureworkflow/wala/WALA/continuous-integration.yml/master?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/continuous-integration.yml:102: update your workflow using https://app.stepsecurity.io/secureworkflow/wala/WALA/continuous-integration.yml/master?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/publish-test-results.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/wala/WALA/publish-test-results.yml/master?enable=pin","Info:   0 out of   6 GitHub-owned GitHubAction dependencies pinned","Info:   1 out of   5 third-party GitHubAction dependencies pinned"],"documentation":{"short":"Determines if the project has declared and pinned the dependencies of its build process.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#pinned-dependencies"}},{"name":"Fuzzing","score":0,"reason":"project is not fuzzed","details":["Warn: no fuzzer integrations found"],"documentation":{"short":"Determines if the project uses fuzzing.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#fuzzing"}},{"name":"Packaging","score":10,"reason":"packaging workflow detected","details":["Info: Project packages its releases by way of GitHub Actions.: .github/workflows/continuous-integration.yml:13"],"documentation":{"short":"Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#packaging"}},{"name":"SAST","score":0,"reason":"SAST tool is not run on all commits -- score normalized to 0","details":["Warn: 0 commits out of 28 are checked with a SAST tool"],"documentation":{"short":"Determines if the project uses static code analysis.","url":"https://github.com/ossf/scorecard/blob/c1d103a9bb9f635ec7260bf9aa0699466fa4be0e/docs/checks.md#sast"}}]},"last_synced_at":"2025-08-22T01:28:45.261Z","repository_id":2931561,"created_at":"2025-08-22T01:28:45.261Z","updated_at":"2025-08-22T01:28:45.261Z"},"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":31400460,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-04-04T10:20:44.708Z","status":"ssl_error","status_checked_at":"2026-04-04T10:20:06.846Z","response_time":60,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["android","callgraph","dataflow-analysis","java","javascript","pointer-analysis","program-analysis","slicing","static-analysis","static-code-analysis"],"created_at":"2025-12-18T00:28:49.528Z","updated_at":"2026-04-04T13:00:59.420Z","avatar_url":"https://github.com/wala.png","language":"Java","readme":"# WALA’s Gradle Build System\n\nThis document describes some WALA-specific aspects of our Gradle build\nsystem, plus a few general Gradle features that may be of particular\ninterest to WALA developers.  However, it is not a Gradle tutorial.\n\n## Getting Started\n\n### External Dependencies: Patience is a Virtue\n\nGradle downloads many packages and supporting Java libraries as\nneeded.  Your first Gradle build may take a long time.  On a fast\nworkstation with a university-grade network and no local caches, my\ninitial run of `./gradlew assemble processTestResources` took five\nminutes.  On a decent laptop with residential DSL and no local caches,\nthe same initial build took twenty minutes.  Fortunately, user- and\nproject-level Gradle caches will make incremental rebuilds much\nfaster.  Rerunning `./gradlew assemble processTestResources` with a\nwarm cache in an already-built tree takes under three seconds.\n\nWALA components are built using a mix of Java 11 and Java 17.  Gradle\nwill\n[download suitable JDKs automatically](https://docs.gradle.org/current/userguide/toolchains.html#sec:provisioning)\nif they are not already\n[locally installed](https://docs.gradle.org/current/userguide/toolchains.html#sec:auto_detection)\nor\n[custom-configured](https://docs.gradle.org/current/userguide/toolchains.html#sec:custom_loc).\n\nGradle itself requires a Java 17 JVM or newer when building and testing WALA.\nFor advice on changing Gradle’s JVM, visit Gradle’s [Configuring the Build\nEnvironment](https://docs.gradle.org/current/userguide/build_environment.html)\ndocumentation and look for discussion of the `org.gradle.java.home` Gradle\nproperty or the `JAVA_HOME` environment variable.\n\n### Eclipse\n\n#### One-Time Eclipse Configuration\n\nTo work with WALA inside Eclipse, first **install Eclipse Buildship\n3.1 or later** using either\n[the Eclipse Marketplace](http://www.vogella.com/tutorials/EclipseGradle/article.html#installation-via-the-marketplace)\nor\n[the Eclipse update manager](http://www.vogella.com/tutorials/EclipseGradle/article.html#installation-via-the-eclipse-update-manager).\nBuildship integrates Eclipse with Gradle, much like how M2Eclipse\nintegrates Eclipse with Maven.  Restart Eclipse after installing this\nfeature.\n\n#### Importing WALA Projects Into Eclipse\n\nOnce you are running a Buildship-enabled Eclipse,\n[use the “Existing Gradle Project” import wizard](http://www.vogella.com/tutorials/EclipseGradle/article.html#import-an-existing-gradle-project)\nto import WALA into Eclipse.  Select and import the topmost level of\nyour WALA source tree.  On the “Import Options” page of the import\nwizard, leave all settings at their defaults: the “Override workspace\nsettings” option should be off, and the grayed-out “Gradle\ndistribution” choice should be set to “Gradle wrapper.” It is also\nrecommended that you clear the \"Gradle user home\" dialog box in the\n**Gradle Preferences** (not the one in the import wizard) prior to\nimporting ([one\nissue](https://github.com/wala/WALA/issues/731#issuecomment-604465043)\nwas resolved this way). You do not need to select each of WALA’s\nsub-projects; import only the top-level WALA source tree, and the rest\nwill follow.\n\nThe first time you import the WALA project, Eclipse will synchronize\nits project model with the Gradle build configuration, including\ndownloading some large supporting libraries.  The “Import Gradle\nProject” wizard may spend tens of minutes showing “Importing root\nproject: Configure project :” with no movement of its progress bar.\nThis is normal.  [Be\npatient](#external-dependencies-patience-is-a-virtue) during the\ninitial project import, especially if you have a slow network\nconnection.\n\nNote: a pristine WALA source tree is *not* pre-configured as a group\nof Eclipse projects.  Using the standard Eclipse “Existing Projects\ninto Workspace” import wizard will not work correctly.  You must\n[use the “Existing Gradle Project” import wizard](http://www.vogella.com/tutorials/EclipseGradle/article.html#import-an-existing-gradle-project)\ninstead.\n\n#### `.classpath` and `.project` as Generated Files\n\nYou will find no `.classpath` or `.project` files anywhere in [the\nGradle fork of WALA’s Git repository](https://github.com/liblit/WALA).\nImporting using the “Existing Gradle Project” wizard creates these\nEclipse project configuration files automatically based on the\nunderlying Gradle configuration.\n\nTherefore, when working with Eclipse + Gradle, you should **treat\n`.classpath` and `.project` files as *generated* artifacts,** not as\nfiles to edit directly or through the Eclipse project configuration\nGUI.  For example, avoid using the Java Build Path settings dialog to\nmake changes that are stored in a `.classpath` file:  the modified\n`.classpath` file is not git-tracked, so your changes will eventually\nbe lost or overwritten.\n\nThe right way to change the contents of any of a `.classpath` or\n`.project` file is to change the Gradle configuration such that the\ngenerated `.classpath` and `.project` files will have the desired\ncontents, likely by using [Gradle’s `eclipse`\nplugin](https://docs.gradle.org/current/userguide/eclipse_plugin.html).\nA few WALA sub-projects already use this:  look for `eclipse.project`\nin `*/build.gradle.kt` for examples.\n\n### IntelliJ IDEA\n\n#### Opening WALA in IntelliJ IDEA\n\nOpen the top-level WALA directory as a project; it should have a\ndistinctive badge on its folder icon marking it as a directory\ncontaining a recognized IntelliJ IDEA project.\n\nThe first time you open the WALA project, IntelliJ IDEA will notify\nyou that “IntelliJ IDEA found a Gradle build script”.  Select the\n“Import Gradle Project” option offered by this notification.  IntelliJ\nIDEA will synchronize its project model with the Gradle build\nconfiguration, including downloading some large supporting libraries.\nThis can take tens of minutes, but is only necessary in a clean,\nnever-previously-built tree.  [Be\npatient](#external-dependencies-patience-is-a-virtue) during the\ninitial project open, especially if you have a slow network\nconnection.\n\n#### Benign Warning About Non-Managed Maven Project\n\nEach time you open the WALA project, IntelliJ IDEA may report\n“Non-managed pom.xml file found” in its event log.  This arises\nbecause WALA historically has built using both Gradle and Maven, but\nWALA in IntelliJ IDEA needs only the Gradle configuration.  You can\nsafely ignore this notification, permanently disable it using the\noffered “Disable notification” link, or even disable the IntelliJ IDEA\nMaven plugin entirely if you have no other need for it.\n\n#### Project Configuration as Derived Model\n\nIntelliJ IDEA automatically derives its project models from the Gradle\nbuild configuration, including all information about both internal and\nexternal build dependencies.  However, this synchronization only goes\nin one direction: from Gradle to IntelliJ IDEA, not from IntelliJ IDEA\nback into Gradle.  If you manipulate the project structure using the\nIntelliJ IDEA’s user interface, your changes will likely be\noverwritten the next time IntelliJ IDEA scans the Gradle build\nconfiguration.\n\nThis particularly applies to settings found in the “Modules” and\n“Libraries” sections of the “Project Structure” dialog.  The right way\nto change module and library settings is to change the Gradle\nconfiguration such that the *derived* IntelliJ IDEA model is what you\nwant it to be.\n\n### Gradle Command Line\n\nYou do not need to install Gradle separately.  **WALA includes its own\ncopy of Gradle, available as the `gradlew` script in the top-level\nWALA directory.** Use this script for all command-line Gradle actions.\nFor example, to compile all of WALA’s main (non-test) code and gather\nit into jar archives, run `./gradlew assemble`.\n\nIn general, most Gradle-generated artifacts will appear somewhere\nunder `*/build`.  For example the jar archives created by the\n`assemble` task can be found as `*/build/libs/*.jar`.  Note, however,\nthat Eclipse-generated artifacts will appear in Eclipse-specific\nplaces, such as `*/bin` and `*/target`.\n\n#### Trustworthy Dependencies For Incremental Builds\n\nGradle has excellent understanding of task and file dependencies.  You\ncan trust it to perform incremental rebuilds rather than always\nrebuilding from scratch.  If you are used to cleaning your build tree\nand rebuilding from scratch after every change, I recommend that you\ndrop `clean` as a reflexive extra step and **trust Gradle to do\nincremental builds correctly.**\n\n#### Favorite Build Tasks\n\nSome useful Gradle tasks include:\n\n- `assemble`: build WALA’s main (non-test) code\n\n- `build`: build all WALA code and run all automated tests\n\n- `javadoc`: build all Javadoc documentation\n\n- `publishToMavenLocal`: install WALA’s jar files under `~/.m2`\n\n- `googleJavaFormat`: reformat all Java code to match WALA project\n  standards\n\n- `clean`: remove all Gradle-generated artifacts\n\n#### Tasks in Specific Sub-Projects\n\nWhen you run `./gradlew` in the top-level WALA directory, any tasks\nyou list will be built in all sub-projects.  For example, `./gradlew\nassemble` builds all non-test WALA jars in all sub-projects.  If you\nwant to build tasks only in specific sub-projects, you have two options:\n\n1. Give the fully qualified name of the sub-project task.  For\n   example, to assemble only the Dalvik jar, you could run `./gradlew\n   :com.ibm.wala.dalvik:assemble`.\n\n1. Run Gradle from within some sub-project directory.  For example, to\n   assemble only the Dalvik jar, you could `cd com.ibm.wala.dalvik`\n   and then run `../gradlew assemble`.  Note the proper relative path\n   to the top-level Gradle script: `../gradle` instead of `./gradlew`.\n\n#### Task Name Abbreviation\n\n[Any build task can be abbreviated](https://docs.gradle.org/current/userguide/command_line_interface.html#_task_name_abbreviation)\nby shortening each camel-case-delimited word in its name.  For\nexample, the `processTestResources` task can probably be abbreviated\nas `procTeRes` or even `pTR`.\n\n#### Useful Command-Line Flags\n\nAmong Gradle’s command-line flags, I have found the following\nparticularly useful:\n\n- [`--continue`](https://docs.gradle.org/current/userguide/command_line_interface.html#sec:continue_build_on_failure):\n  keep building non-dependent sub-tasks even after an initial failure.\n  Especially useful in conjunction with the `build` or `test` tasks to\n  see multiple test failures rather than giving up after the first\n  failure.\n\n- [`-t`, `--continuous`](https://docs.gradle.org/current/userguide/command_line_interface.html#_continuous_build):\n  keep Gradle process running and re-execute the given tasks whenever\n  input files change.  Similar to Eclipse’s behavior of updating the\n  build whenever you change and save a file.\n\n- [`--tests=…`](https://docs.gradle.org/current/userguide/java_plugin.html#test_filtering):\n  run only the selected tests.  Use in conjunction with the `build` or\n  `test` tasks for faster turnaround if you are focusing on getting\n  just one or a few failing tests to pass.\n\n- [`--scan`](https://scans.gradle.com/): upload a detailed report of\n  the build process to a Gradle-hosted server for further exploration\n  and analysis.  The only security here is the obscurity of the\n  generated URL for the build report.  If you are not concerned about\n  potentially making your build details public, then `--scan` is a\n  good way to gain insights into why Gradle did what it did, and how\n  long each piece took.\n\n#### Composite Builds\n\nGradle’s [composite\nbuilds](https://docs.gradle.org/current/userguide/composite_builds.html)\nallow a Gradle-managed project to recursively include other\nGradle-managed projects, with Gradle managing the entire build process\nin a coherent, integrated manner.  Thus, if you use Gradle to build\nyour WALA-based project, you can easily have it use WALA from your\nown, private WALA tree instead of from `~/.m2` or the public Maven\nrepository.\n\nThis is especially useful if you frequently find yourself switching\nbetween multiple different personal or experimental WALA builds.  By\navoiding `~/.m2`, each WALA-based project can be its own composite\nbuild, with its own WALA subtree, and no project interferes with any\nother.\n\n\u003c!--\nLocalWords:  processTestResources pre classpath gradlew mvn\nLocalWords:  javadoc buildship issuecomment\n--\u003e\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fwala%2Fwala","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fwala%2Fwala","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fwala%2Fwala/lists"}