Install groovy with Homebrew, chocolatey, apt, MacPorts, Nix, pacman, scoop

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• grape
• groovy
• groovyConsole
• groovyc
• groovydoc
• groovysh
• java2groovy
• startGroovy

Project history

The Groovy project dates itself to 2003, and the official site copyright span begins in 2003. Early public release history is visible in the official changelog, which lists beta releases beginning in December 2003 and JSR-labeled releases through 2005 and 2006.

Groovy entered the Java Community Process as JSR 241, an effort to standardize the Groovy programming language for the Java platform. The official changelog records Groovy 1.0.0 on 2007-01-03, after years of beta, release-candidate, and JSR-tagged builds.

Groovy 2.0.0 was released in 2012. Its release notes highlighted static type checking and static compilation, helping Groovy serve both dynamic scripting and more performance-conscious JVM code paths.

In 2015, the Groovy project moved into the Apache Software Foundation incubator. Apache's incubator status page records that Groovy graduated on 2015-11-18, establishing Apache Groovy as an ASF top-level project governed under Apache processes.

Later major lines kept the language aligned with modern Java while retaining its scripting and DSL identity. The official changelog records Groovy 3.0.0 in 2020, Groovy 4.0.0 in 2022, and Groovy 5.0.0 in 2025.

Adoption history

Groovy's adoption came from being close enough to Java for enterprise teams while adding concise syntax, closures, builders, runtime metaprogramming, and script execution. That made it useful for build logic, tests, internal automation, and DSL-heavy frameworks.

The Groovy ecosystem became especially visible through Grails, Gradle build scripts, Spock tests, Jenkins Pipeline scripts, and many smaller Java-platform automation tasks. The official home page describes a vibrant ecosystem across web development, reactive applications, concurrency, test frameworks, build tools, code analysis, and GUI building.

Apache governance mattered for adoption because it moved Groovy from its Codehaus-era identity into ASF infrastructure, releases, trademarks, and community processes. That gave packagers a stable upstream identity and helped downstream projects refer to Apache Groovy rather than a vendor-owned runtime.

How it is used

The Homebrew `groovy` package installs command-line entry points such as `groovy`, `groovyc`, `groovysh`, `groovyConsole`, `groovydoc`, `grape`, `java2groovy`, and `startGroovy`.

`groovy` runs scripts and classes on the JVM; `groovyc` compiles Groovy sources; `groovysh` provides a shell; `groovyConsole` provides a Swing console; `groovydoc` builds API documentation; and `grape` handles Groovy's dependency-grabbing workflow.

User-level files under `~/.groovy` are part of the package curation because Grape, logging, and shell startup customization are common per-user Groovy workflows. No general credentials file is documented for the language runtime.

Why package nerds care

Groovy is a packaging hinge for the JVM scripting world. A single language package exposes a REPL, compiler, script runner, dependency helper, and documentation generator while depending on Java rather than shipping an isolated VM.

It also sits at the intersection of language-runtime packaging and build-tool culture. Many developers meet Groovy through tools that embed it, but the package remains valuable for direct scripts, local debugging, and running examples outside a larger framework.

For package maintainers, Groovy is interesting because the project has long-lived major lines, Apache source-release expectations, Java-version compatibility concerns, and a split between the language distribution and SDK/documentation adjunct packages.

Timeline

• 2003: Groovy project history begins, with beta releases listed in the official changelog.
• 2004: JSR 241 tracked Groovy standardization work for the Java platform.
• 2007: Groovy 1.0.0 was released.
• 2012: Groovy 2.0.0 introduced static type checking and static compilation as headline features.
• 2015: Groovy entered Apache incubation and graduated as an Apache top-level project on 2015-11-18.
• 2020: Groovy 3.0.0 was released.
• 2022: Groovy 4.0.0 was released.
• 2025: Groovy 5.0.0 was released.

Related projects

• Grails is the historically important Groovy web framework.
• Gradle popularized Groovy DSL usage for JVM builds.
• Spock is a Groovy-based testing and specification framework.
• Jenkins Pipeline made Groovy scripts a common CI/CD automation surface.
• Grape is Groovy's dependency-grabbing system exposed by the `grape` command.

Sources

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