# Installer grails avec Homebrew, MacPorts, Nix, chocolatey, scoop

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de grails pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:grails
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install grails
```

  Preuve: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install grails
```

  Preuve: MacPorts ports tree: devel/grails/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#grails
```

  Preuve: nixpkgs package indexes: grails from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix

### Windows

- Chocolatey (92%):

```sh
choco install Grails
```

  Preuve: Chocolatey community package catalog: Grails from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='7.3108','pragmaticworksworkbenchserver'

- Scoop (92%):

```sh
scoop install main/grails
```

  Preuve: Scoop official bucket manifest trees: bucket/grails.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

## Faits du paquet

- **Clé du paquet:** brew:grails
- **Gestionnaire de paquets:** Homebrew
- **Version:** 7.2.1
- **Résumé source:** Web application framework for the Groovy language
- **Page d'accueil:** <https://grails.apache.org/>
- **Dépôt:** <https://github.com/apache/grails-core>
- **Dernière mise à jour:** 2026-07-17T08:45:37Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- grails (alias)
- grails-forge-cli (alias)
- grails-shell-cli (alias)
- grails_forge_cli_completion (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 7.2.1
## Historique du projet et usages

Apache Grails is a Groovy-based full-stack web application framework for the JVM. It packages a convention-over-configuration application generator, runtime conventions, Gradle-based builds, GORM data access, and Spring Boot integration into a CLI-centered developer workflow.

### Historique du projet

The Apache Grails project history says work began in July 2005, followed by a 0.1 release on March 29, 2006 and a 1.0 release on February 5, 2008. Its early appeal came from bringing Ruby on Rails-style productivity to the Java and Groovy ecosystem.

Grails passed through several stewardship phases: G2One, SpringSource, Object Computing, the Grails Foundation and Unity Foundation, and then the Apache Software Foundation. Apache described the ASF migration as an 18-month process starting in late spring 2024 alongside Grails 7 development.

The ASF move also changed package coordinates for Grails artifacts to org.apache.grails and consolidated many repositories into a single code base to satisfy ASF policy and speed release work.

### Historique d'adoption

Grails gained adoption among JVM teams that wanted rapid web application development without leaving Java infrastructure. Its docs emphasize productivity, DRY conventions, Groovy, Spring Boot, Hibernate/GORM, and plugin-based extension.

Package managers matter for Grails because the CLI creates and runs applications, invokes scaffolding and build tasks, and anchors a developer's local JVM web framework toolchain. Homebrew, SDKMAN, and similar managers made it easier to install the framework outside IDE-specific setup.

### Modes d'utilisation

A typical Grails package user installs the CLI, creates or opens a Grails app, edits build.gradle and grails-app/conf configuration, and runs framework commands to build, test, run, generate, or package an application.

The framework is used for full-stack server-rendered apps, REST APIs, and JVM services that benefit from Groovy productivity while retaining Spring Boot, Jakarta EE, Hibernate, and Gradle integration.

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

Grails is significant because it is a framework package whose executable is the front door to an entire application layout. Its package has to fit JVM versioning, Gradle behavior, shell completion, generated project files, and long-lived enterprise upgrade paths.

The Apache transition is especially relevant for packagers because artifact coordinates, source distribution rules, release signing, and repository layout all affect downstream formulae and build reproducibility.

### Chronologie

- 2005-07: Work on Grails began.
- 2006-03-29: Grails 0.1 release.
- 2008-02-05: Grails 1.0 release.
- 2019-07-11: Grails 4 GA release announced.
- 2024: ASF migration began alongside Grails 7 development.
- 2025-06-10: Grails 7.0.0-M4 became the first Grails release under ASF incubation.
- 2025-10-07: Apache Grails graduated to an ASF Top-Level Project.

### Related projects

- Apache Groovy is the language foundation.
- Spring Boot, Spring Framework, Jakarta EE, Hibernate, GORM, Gradle, and Grails Forge are core parts of the Grails ecosystem.
- Ruby on Rails is the historical convention-over-configuration comparison point.

### Sources

- <https://grails.apache.org/blog/2025-06-10-grails-7-m4.html>
- <https://grails.apache.org/blog/2025-10-07-apache-grails-graduation-top-level-project.html>
- <https://grails.apache.org/docs/latest/guide/single.html>
- <https://grails.apache.org/docs/latest/guide/upgrading.html>
- <https://grails.apache.org/documentation.html>


## Notes de sécurité

generalized runtime or code generation signal.

- **Risque Geiger:** yellow / moyen
- generalized runtime or code generation signal


## 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: build.gradle, grails-app/conf/application.yml, grails-app/conf/application.groovy, grails-app/conf/runtime.groovy, ./config/application.(properties|yml), ./application.(properties|yml), grails-app/conf/logback-spring.xml
## Autres enregistrements de gestionnaires de paquets

- Nix - grails: normalized package name match | nixpkgs package indexes: grails from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix
- MacPorts - grails: normalized package name match | MacPorts ports tree: devel/grails/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Chocolatey - Grails: normalized package name match | Chocolatey community package catalog: Grails from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='7.3108','pragmaticworksworkbenchserver'
- Scoop - main/grails: normalized package name match | Scoop official bucket manifest trees: bucket/grails.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/grails.yml](https://github.com/mxcl/pkgdb/blob/main/combined/grails.yml)


## Sources

- 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