> For the complete documentation index, see [llms.txt](https://docs.meterian.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meterian.io/the-client/command-line-parameters/specific-controls/gradle-specific-controls.md). # Gradle specific controls This is a list of system flags that can be used to request specific Gradle behaviours. Please refer to the parent section to learn how to specify them to the client. `gradle.root.only=false` When true, forces the scanner to recursively traverse the directory path, analysing all Gradle projects present. By default, the client looks only in the root folder. `gradle.kts.dependency.set=dependencies` When using Gradle powered by Kotlin, it may be required to tell the scanner which configuration of dependencies it should take under consideration. For example, for an Android application, the value of such variable will be usually "`app.dependencies`" rather than the default value "`dependencies`". `gradle.configurations=implementation,test,release` When used, it allows to select which gradle configuration should be taken in account when executing the analysis. By default, all configurations are taken in account. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.meterian.io/the-client/command-line-parameters/specific-controls/gradle-specific-controls.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.