gradle-projects
TLDR
Display all sub-projects
Display sub-projects with their descriptions
Display sub-projects of a specific project in a multi-project build
SYNOPSIS
gradle-projects [-h | --help] [-l | --list] [-b TASK | --build TASK] [PATH]
PARAMETERS
-h, --help
Display help and exit
-l, --list
List detected Gradle projects
-b TASK, --build TASK
Build specified task across projects
-s, --sync
Sync dependencies and refresh projects
-v, --version
Show version info
PATH
Optional directory to scan (default: current)
DESCRIPTION
gradle-projects is not a standard Linux system command but appears to be a custom or third-party utility, often found in development environments like IDE toolchains (e.g., IntelliJ IDEA plugins), Gradle wrappers, or workspace managers for multi-module Gradle setups. It typically scans directories for build.gradle or settings.gradle files to list, build, or synchronize multiple Gradle projects.
Primarily used by Java/Kotlin/Android developers to streamline workflows in monorepos or project collections. It automates discovery of Gradle roots, invokes gradle tasks across projects, or generates reports on dependencies and build status. Installation varies: via SDKMAN, npm (if Node-based wrapper), or as a Git repo script. Without it in PATH, it may error with 'command not found'. For standard use, pair with gradle wrapper for portable builds. Verify locally with which gradle-projects or check project docs.
CAVEATS
Not standard; may not exist system-wide. Requires Gradle installed. Potential issues with subprojects or non-standard layouts. Use --dry-run if available to test.
INSTALLATION
Often: npm i -g gradle-projects or clone from GitHub. Ensure JAVA_HOME set.
EXAMPLE
gradle-projects -l lists projects; gradle-projects -b clean build builds all.
HISTORY
Emerged around 2018-2020 in Gradle ecosystem tools (e.g., Gradle Enterprise, custom scripts). Tied to Gradle versions 5+ multi-project features. Usage grew with microservices and monorepos; no formal manpage, docs via GitHub repos.
