# 使用 Homebrew, apk, chocolatey, apt, MacPorts, Nix, pacman, scoop 安装 gradle 查看 gradle 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。 ## 安装 ```sh sudo av install brew:gradle ``` 其他安装命令: ### macOS - Homebrew (100%): ```sh brew install gradle ``` 证据: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install gradle ``` 证据: MacPorts ports tree: devel/gradle/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Linux - apk (92%): ```sh sudo apk add gradle ``` 证据: Alpine Linux edge package indexes: gradle from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz - Debian apt (92%): ```sh sudo apt install gradle ``` 证据: Debian stable package indexes: gradle from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz - Nix (92%): ```sh nix profile install nixpkgs#gradle ``` 证据: nixpkgs package indexes: gradle from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix - pacman (92%): ```sh sudo pacman -S gradle ``` 证据: Arch Linux sync databases: gradle from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ### Windows - Chocolatey (92%): ```sh choco install gradle ``` 证据: Chocolatey community package catalog: gradle from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','google-workspace-sync' - Scoop (92%): ```sh scoop install main/gradle ``` 证据: Scoop official bucket manifest trees: bucket/gradle.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## 软件包事实 - **软件包键:** brew:gradle - **软件包管理器:** Homebrew - **版本:** 9.6.1 - **来源摘要:** Open-source build automation tool based on the Groovy and Kotlin DSL - **主页:** - **最后更新:** 2026-06-26T19:52:00Z - **已生成:** 2026-08-03T19:37:03+00:00 ## 可执行文件 - gradle (别名) ## 安装行为 - Bottle: 不可用 ## 版本和新鲜度 - 页面生成时间: 2026-08-03 - 管理器版本: 9.6.1 ## 项目历史与用法 Gradle is an open-source build automation tool for multi-language software projects, especially JVM and Android builds. Its package-manager identity is the `gradle` CLI, but most projects actually standardize on the Gradle Wrapper so a repository can declare the Gradle distribution it expects. Gradle became important because it combined ideas from earlier build tools with a programmable Groovy and later Kotlin DSL, task graph execution, dependency management, plugins, daemons, caching, and integration with IDEs and CI. ### 项目历史 Gradle's own documentation describes builds as projects and tasks configured by build scripts written in Groovy or Kotlin. The project structure convention centers on `settings.gradle(.kts)`, `build.gradle(.kts)`, and the wrapper scripts `gradlew` and `gradlew.bat`. Gradle 1.0, released on June 12, 2012 according to the official release index, was framed by its release notes as a major step for Gradle and build tools. That release replaced Ivy-based dependency resolution with a Gradle dependency engine, improved dependency caching, added daemon performance work, expanded Java quality plugins, and emphasized enterprise-scale builds. Gradle's official evolution article summarizes the major-version arc: 2.0 improved performance, memory efficiency, dependency management, and incremental build support; 3.0 enabled the daemon by default and improved IDE/Kotlin DSL support; 4.0 made build cache production-ready for Java and Groovy compilation; 5.0 made Kotlin DSL production-ready and added Java 11 support; 6.0 introduced enhanced dependency management metadata; 7.0 focused on incremental builds, dependency verification, and Java 16 support; 8.0 emphasized configuration-cache behavior and parallelism. ### 采用历史 Gradle spread through JVM projects because it offered programmable build logic while still providing conventions through plugins. Android adoption made Gradle part of a massive mobile build ecosystem: Android Studio projects expose Gradle wrapper files, settings files, top-level and module-level build files, and Gradle properties as standard project artifacts. The wrapper changed package-manager expectations. A developer may install `gradle` with Homebrew to bootstrap or run ad hoc builds, but many repositories prefer `./gradlew` so the checked-in wrapper properties select the project Gradle version. This made Gradle unusually friendly to mixed-version repositories and CI environments. Gradle also became a platform for build-performance tooling. Official docs and adjacent Gradle products emphasize build scans, daemon reuse, build cache, configuration cache, and profiling workflows, reflecting a culture where the build tool is both dependency resolver and performance-critical infrastructure. ### 使用方式 At the command line, developers run tasks such as `gradle build`, `gradle test`, or `gradle clean build`, but Gradle documentation recommends the wrapper for most existing projects. Build scripts define tasks, plugins, dependencies, repositories, and project conventions. The common files are package-ecosystem signals: `settings.gradle` or `settings.gradle.kts` defines root and subprojects; `build.gradle` or `build.gradle.kts` defines build logic; `gradle.properties` configures Gradle or project properties; and files under the Gradle user home configure user-wide behavior such as init scripts. Gradle's DSL and plugin system make it a host for ecosystems rather than only a command runner. Java, Groovy, Kotlin, Scala, Android, C/C++, JavaScript, and Kotlin Multiplatform projects all appear in the official documentation as supported languages or frameworks. ### 为什么软件包爱好者会关心 Gradle is significant to package nerds because it is itself a package manager, dependency resolver, task scheduler, and project metadata interpreter. A Gradle installation can decide which artifacts are fetched, how versions are aligned, when tasks are up to date, and which generated outputs are reproducible. It also forces distribution questions: should a system package provide one Gradle CLI, should a project use the wrapper, how should checksums and distribution URLs be audited, and how should old major versions remain available when enterprise or Android builds cannot immediately migrate? For Homebrew, the unversioned `gradle` formula serves users who want a general CLI installation, while versioned formulae such as `gradle@7` and `gradle@8` serve projects pinned to a major line. ### 时间线 - 2009: The official release index lists Gradle 0.8. - 2012: Gradle 1.0 released with rebuilt dependency resolution, improved dependency cache, daemon performance work, quality plugins, and Tooling API emphasis. - 2014: Gradle 2.0 improved performance, memory efficiency, dependency management, and incremental build support. - 2016: Gradle 3.0 enabled the daemon by default and improved IDE/Kotlin DSL support. - 2017: Gradle 4.0 made build cache production-ready for Java and Groovy compilation. - 2018: Gradle 5.0 made Kotlin DSL production-ready and supported Java 11. - 2019: Gradle 6.0 introduced enhanced dependency management with a new metadata format. - 2021: Gradle 7.0 added Java 16 support, Apple Silicon support, and experimental version catalogs. - 2023: Gradle 8.0 expanded configuration-cache execution behavior and Java toolchain configuration. ### Related projects - Apache Ant, Apache Maven, Ivy, Make, SCons, and Bazel are adjacent build and dependency-management tools. - Android Gradle Plugin and Android Studio are major downstream Gradle ecosystem pieces. - Develocity, Gradle Build Scan, Gradle Profiler, and Gradle Plugin Portal are closely related Gradle ecosystem services or tools. - Groovy and Kotlin are central to Gradle's build-script DSL story. ### 来源 - - - - - - - - ## 安全说明 build system capable of executing project logic. - **Geiger 风险:** yellow / 高 - build system capable of executing project logic ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ~/.gradle/gradle.properties, ~/.gradle/init.d/*.gradle, ./gradle.properties, ./settings.gradle(.kts), ./build.gradle(.kts) - Windows: C:\Users\\.gradle\gradle.properties, C:\Users\\.gradle\init.d\*.gradle, .\gradle.properties, .\settings.gradle(.kts), .\build.gradle(.kts) ## 其他软件包管理器记录 - Debian apt - gradle - 4.4.1-22: normalized package name match | Debian stable package indexes: gradle from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Powerful build system for the JVM | https://gradle.org - Debian apt - gradle-doc - 4.4.1-22: normalized package name match | Debian stable package indexes: gradle-doc from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Powerful build system for the JVM - Documentations | https://gradle.org - Debian apt - libgradle-core-java - 4.4.1-22: normalized package name match | Debian stable package indexes: libgradle-core-java from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Powerful build system for the JVM - Core libraries | https://gradle.org - Debian apt - libgradle-plugins-java - 4.4.1-22: normalized package name match | Debian stable package indexes: libgradle-plugins-java from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | Powerful build system for the JVM - All plugins | https://gradle.org - Nix - gradle: normalized package name match | nixpkgs package indexes: gradle from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix - Ubuntu apt - gradle - 4.4.1-20: normalized package name match | Ubuntu 24.04 LTS package indexes: gradle from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Powerful build system for the JVM | https://gradle.org - Ubuntu apt - gradle-doc - 4.4.1-20: normalized package name match | Ubuntu 24.04 LTS package indexes: gradle-doc from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Powerful build system for the JVM - Documentations | https://gradle.org - Ubuntu apt - libgradle-core-java - 4.4.1-20: normalized package name match | Ubuntu 24.04 LTS package indexes: libgradle-core-java from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Powerful build system for the JVM - Core libraries | https://gradle.org - Ubuntu apt - libgradle-plugins-java - 4.4.1-20: normalized package name match | Ubuntu 24.04 LTS package indexes: libgradle-plugins-java from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Powerful build system for the JVM - All plugins | https://gradle.org - apk - gradle - 8.14.4-r0: normalized package name match | Alpine Linux edge package indexes: gradle from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz | Build tool with a focus on build automation and support for multi-language development | https://gradle.org/ - pacman - gradle - 9.6.1-1: normalized package name match | Arch Linux sync databases: gradle from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Powerful build system for the JVM | https://gradle.org/ - MacPorts - gradle: normalized package name match | MacPorts ports tree: devel/gradle/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 - Chocolatey - gradle: normalized package name match | Chocolatey community package catalog: gradle from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','google-workspace-sync' - Scoop - main/gradle: normalized package name match | Scoop official bucket manifest trees: bucket/gradle.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/gradle.yml](https://github.com/mxcl/pkgdb/blob/main/combined/gradle.yml) ## 来源 - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph