tldr-pages/tldr

Let's document: gradle

Open

#19,101 opened on Oct 29, 2025

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Shell (2,507 forks)batch import
help wantedlet's documentnew command

Repository metrics

Stars
 (30,937 stars)
PR merge metrics
 (Avg merge 7d 5h) (321 merged PRs in 30d)

Description

Command description

Gradle is a build tool for managing dependencies, plugins, and project automation. It includes many CLI commands with various flags and options. Documenting these commands will help new learners understand Gradle quickly and provide a single reference point for experienced users as a refresher.

Documentation

https://docs.gradle.org/current/userguide/command_line_interface.html

Platform

Common

VCS repository link (e.g. GitHub, GitLab)

https://github.com/gradle/gradle

Additional information

No response

Commands

  • gradle - #495

Standard (Core)

  • build - #19273
  • clean - #20558
  • dependencies - #20558
  • dependencyInsight - #20558
  • init - #20558
  • projects - #20558
  • properties - #20558
  • tasks - #20558
  • test - #20558
  • wrapper - #20558

Java Plugin

  • assemble
  • check
  • classes
  • compileJava
  • jar
  • javadoc

Application Plugin

  • installDist
  • run

Publishing

  • publish
  • publishToMavenLocal

Android Plugin

  • assembleDebug
  • assembleRelease
  • connectedAndroidTest
  • installDebug
  • lint

Spring Boot Plugin

  • bootBuildImage
  • bootJar
  • bootRun
  • bootWar

Contributor guide

Research direction
Pick an undocumented command from the list, read the Gradle documentation, and create a tldr page following the contributing guidelines.
Tech stack
None
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90