Installer groovysdk avec Homebrew

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• grape_completion
• groovy.ico
• groovyConsole_completion
• groovy_completion
• groovyc_completion
• groovydoc_completion
• groovysh_completion

Historique du projet

Apache Groovy began in 2003 as a Java-platform language and evolved through beta, JSR, release-candidate, and 1.0.0 releases documented in the official changelog. JSR 241 records the Java Community Process standardization effort for Groovy.

Groovy 2.0.0 in 2012 added static type checking and static compilation to the language's dynamic scripting model. In 2015, the project entered the Apache Incubator and graduated on 2015-11-18 as an Apache top-level project.

The package role is narrower than the main `groovy` formula: `groovysdk` is curated as SDK material for Groovy, with completion assets and documentation-oriented support around the same Apache Groovy upstream.

Historique d'adoption

The Groovy SDK is relevant because Groovy users rarely consume only a compiler. They use shell commands, documentation, dependency tooling, completions, and editor or terminal support around a JVM language distribution.

Groovy adoption in build tools, CI pipelines, frameworks, and test tooling made SDK-adjacent packaging useful: completions and command support reduce friction for users who run Groovy tools directly from a Unix shell.

Modes d'utilisation

The Homebrew package exposes completion-oriented files such as `groovy_completion`, `groovyc_completion`, `groovysh_completion`, `groovyConsole_completion`, `groovydoc_completion`, and `grape_completion` rather than the main runtime command set.

Because it shares Apache Groovy's per-user conventions, the curation preserves the same `~/.groovy` configuration paths used by Grape, logging, and shell initialization. No separate credentials file is documented for this SDK package.

Pourquoi les passionnés de paquets s'y intéressent

`groovysdk` is package-nerd interesting mostly as a split-package artifact: it shows how package managers sometimes separate a language runtime from SDK or shell-support assets even when the upstream project is one language distribution.

The package also makes Groovy friendlier in CLI-heavy environments by shipping completions for the commands developers use when compiling, documenting, running, and exploring Groovy code.

Chronologie

• 2003: Groovy project history begins.
• 2007: Groovy 1.0.0 was released.
• 2012: Groovy 2.0.0 was released with static type checking and static compilation.
• 2015: Groovy graduated from Apache incubation.
• 2020: Groovy 3.0.0 was released.
• 2022: Groovy 4.0.0 was released.
• 2025: Groovy 5.0.0 was released.

Related projects

• Apache Groovy is the upstream project for this package role.
• The main Homebrew `groovy` package provides the runtime commands that the SDK completion files accompany.
• Grape, Groovysh, Groovyc, Groovydoc, and GroovyConsole are the command surfaces reflected by the package contents.

Sources

• https://github.com/apache/groovy
• https://groovy-lang.org/changelogs.html
• https://groovy-lang.org/releasenotes/groovy-2.0.html
• https://groovy.apache.org/download.html
• https://incubator.apache.org/projects/groovy.html
• https://jcp.org/en/jsr/detail?id=241
• https://www.groovy-lang.org/
• https://www.groovy-lang.org/documentation.html