You can also invoke Gradle via its <<command_line_interface.adoc#command_line_interface,command-line interface>> (CLI) in your terminal or through your continuous integration (CI) server.

== Education
The **<<about_manual.adoc#about_manual,Gradle User Manual>>** is the official documentation for the Gradle Build Tool.

Laura Kassovic <******@****.***> 1701107622 -0800

Laura Kassovic <******@****.***> 1701107622 -0800

| <<groovy_plugin.adoc#groovy_plugin,Groovy>>
| Adds Groovy configuration to `.project` file.

| <<scala_plugin.adoc#scala_plugin,Scala>>
| Adds Scala support to `.project` and `.classpath` files.

| <<war_plugin.adoc#war_plugin,War>>
| Adds web application support to `.project` file.

| <<ear_plugin.adoc#ear_plugin,Ear>>
| Adds ear application support to `.project` file.
|===

*Always*::
Generates an IDEA module file. Also generates an IDEA project and workspace file if the project is the root project.

*<<java_plugin.adoc#java_plugin,Java Plugin>>*::
Additionally adds Java configuration to the IDEA module and project files.

[[writing_settings_files]]
= Writing Settings Files

The settings file is the entry point of every Gradle build.

image::author-gradle-7.png[]

Early in the Gradle Build lifecycle, the <<build_lifecycle.adoc#sec:initialization,initialization phase>> finds the settings file in your <<directory_layout#dir:project_root,project root directory>>.

The introduction covers:

<<gradle_directories.adoc#gradle_directories,Part 1.>> Gradle Directories +
<<intro_multi_project_builds.adoc#intro_multi_project_builds,Part 2.>> Multi-Project Builds +
<<build_lifecycle.adoc#build_lifecycle,Part 3.>> Gradle Build Lifecycle +
<<writing_settings_files.adoc#writing_settings_files,Part 4.>> Writing Settings Files +
<<writing_build_scripts.adoc#writing_build_scripts,Part 5.>> Writing Build Scripts +

=== Automatic injection with the Java Gradle Plugin Development plugin

The <<java_gradle_plugin.adoc#java_gradle_plugin,Java Gradle Plugin development plugin>> can be used to assist in the development of Gradle plugins.
Starting with Gradle version 2.13, the plugin provides a direct integration with TestKit.
When applied to a project, the plugin automatically adds the `gradleTestKit()` dependency to the `testApi` configuration.

Aggregate task that performs verification tasks, such as running the tests.
Some plugins add their own verification task to `check`.
 For example, the <<xctest_plugin.adoc#xctest_plugin,XCTest Plugin>> attaches a task to this lifecycle task to run tests.
This task is added by the <<base_plugin.adoc#base_plugin,Base Plugin>>.

`build` - Task (lifecycle)::
Depends on: `check`, `assemble`
::
Aggregate tasks that perform a full build of the project.

This means that changes to order and timestamps in jars on the test classpath will not cause the task to be out-of-date or change the build cache key.
For achieving <<build_cache_concepts.adoc#stable_task_inputs,stable task inputs>> you can also wield the power of <<build_cache_concepts.adoc#filter_runtime_classpath,filtering the runtime classpath>>.