# Gradle — Adaptable Build Automation for JVM and Beyond

> A powerful build tool for Java, Kotlin, Groovy, Scala, Android, and C/C++ projects with incremental builds and a rich plugin ecosystem.

## Install

Save in your project root:

# Gradle — Adaptable Build Automation for JVM and Beyond

## Quick Use
```bash
# Install via SDKMAN
sdk install gradle
# Initialize a new project
gradle init --type java-application
# Build
gradle build
```

## Introduction
Gradle is a build automation tool that combines the flexibility of Ant with the convention-over-configuration approach of Maven. It uses a Groovy or Kotlin DSL instead of XML, supports incremental and cached builds, and powers the Android build system. Gradle handles everything from compiling code to publishing artifacts across polyglot projects.

## What Gradle Does
- Builds, tests, and packages JVM applications (Java, Kotlin, Groovy, Scala)
- Serves as the official build system for Android app development
- Supports C/C++ and Swift projects through native plugins
- Provides build caching and incremental compilation to speed up development
- Manages dependency resolution with support for Maven Central, Ivy, and custom repositories

## Architecture Overview
Gradle uses a directed acyclic graph (DAG) of tasks with dependency tracking. The build lifecycle has three phases: initialization (determines which projects to include), configuration (constructs the task graph), and execution (runs selected tasks). The Gradle Daemon keeps a long-lived JVM process warm to avoid startup overhead. Build Cache stores task outputs locally or remotely so unchanged tasks can be skipped entirely.

## Self-Hosting & Configuration
- Install via SDKMAN, Homebrew, or the Gradle Wrapper (`gradlew`) checked into your repository
- Use `gradle wrapper` to pin a specific Gradle version for reproducible builds
- Configure builds in `build.gradle.kts` (Kotlin DSL) or `build.gradle` (Groovy DSL)
- Set JVM options in `gradle.properties` (e.g., `org.gradle.jvmargs=-Xmx4g`)
- Enable remote build cache with `buildCache { remote<HttpBuildCache> { url = uri("...") } }`

## Key Features
- Kotlin DSL with full IDE autocompletion and type safety for build scripts
- Build Scan service provides shareable, detailed reports of build performance
- Composite builds let you develop libraries and applications together without publishing
- Configuration cache serializes the task graph to skip configuration on repeat builds
- Rich plugin ecosystem for code quality, publishing, containerization, and more

## Comparison with Similar Tools
- **Maven** — XML-based, rigid convention; Gradle offers more flexibility and faster incremental builds
- **Bazel** — optimized for massive monorepos; Gradle is more approachable for typical JVM projects
- **Ant** — low-level and imperative; Gradle adds conventions, dependency management, and caching
- **sbt** — Scala-focused; Gradle covers a broader language ecosystem
- **Pants** — polyglot monorepo tool; Gradle is more widely adopted with a larger plugin ecosystem

## FAQ
**Q: Should I use the Groovy or Kotlin DSL?**
A: Kotlin DSL is recommended for new projects. It provides type-safe accessors and better IDE support.

**Q: How does the Gradle Wrapper work?**
A: The wrapper script (`gradlew`) downloads the exact Gradle version specified in `gradle-wrapper.properties`, ensuring consistent builds without requiring a global install.

**Q: Can Gradle replace Maven for existing projects?**
A: Yes. Gradle can consume Maven POM files, use the same repository layout, and even run a `gradle init` conversion on an existing Maven project.

**Q: What is a Build Scan?**
A: A web-based report that shows task execution times, dependency resolution details, and build failures. Share the link with your team for debugging.

## Sources
- https://github.com/gradle/gradle
- https://docs.gradle.org/

---
Source: https://tokrepo.com/en/workflows/4b29d92b-3a9a-11f1-9bc6-00163e2b0d79
Author: AI Open Source