Install helidon with Homebrew

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• helidon

Project history

Helidon itself was published as Java libraries for writing microservices, with the main repository metadata recording a public GitHub project in August 2018. The project exposes two programming models: Helidon SE, a smaller functional-style API, and Helidon MP, a MicroProfile-oriented runtime for developers who want familiar enterprise Java APIs.

Helidon 2.0 is the key milestone for the package in this batch because the official Helidon 2 documentation says one of that release's new features was the Helidon command-line interface. The CLI let developers create a new application, build it, run it, and perform other project tasks with simple commands, turning Helidon setup from Maven-archetype knowledge into a discoverable tool workflow.

The build-tools repository, also recorded by GitHub metadata in August 2018, contains the CLI implementation and supporting Maven/plugin infrastructure. Its CLI README describes `helidon init` for archetype-based project creation and `helidon dev` for a continuous edit-compile-restart development loop. It also records later changes in how the CLI discovers available Helidon versions and archetype metadata from helidon.io.

Helidon 4 reshaped the framework around Project Nima, replacing the Netty-based reactive web server and web client with virtual-thread-based implementations. The official Helidon 4 docs describe a blocking style API enabled by Java virtual threads, and the Nima page presents it as part of Helidon 4. That matters to the CLI because generated projects and selected archetypes track the framework's major-version model.

Adoption history

Helidon adoption has been driven by Java microservice developers who want either a lightweight SE API or a MicroProfile implementation with health checks, metrics, tracing, OpenAPI, security, gRPC, reactive messaging, and cloud-native integrations. The CLI lowered the cost of trying those paths by generating projects and running the development loop locally.

The Homebrew package is significant because the CLI is distributed as a standalone executable for macOS, Linux, and Windows, while Helidon libraries themselves are consumed from Maven coordinates. A package-manager install therefore gives developers the non-Maven bootstrap tool that creates the Maven project.

How it is used

The official CLI docs describe installation of a standalone `helidon` executable, `helidon init` for creating a project, `helidon dev` for automatic recompilation and restart while editing, and `helidon version` for verification. The build-tools README adds that the CLI uses archetypes, catalogs, and metadata files hosted from helidon.io to select Helidon versions and templates.

The CLI is most useful at the project boundary: choosing a Helidon version, selecting SE or MP, choosing an application type, naming Maven coordinates, generating source, and keeping a local service running while code changes. After that point, normal Java/Maven tooling takes over.

Why package nerds care

For package nerds, Helidon CLI is a neat split-brain package: the framework is a Maven ecosystem artifact, but the onboarding tool is a native-ish command-line executable that package managers can distribute. That makes the Homebrew formula less about shipping the framework and more about placing a project generator on `PATH`.

It also tracks a major Java ecosystem story: a framework that began in the cloud-native reactive/MicroProfile wave, added a CLI in its 2.0 line, and then used Java virtual threads in Helidon 4 to offer blocking-style code with high-concurrency ambitions.

Timeline

• 2018: GitHub metadata records public Helidon and Helidon build-tools repositories.
• Helidon 2.0: Official documentation identifies the Helidon command-line interface as a new feature for creating, building, and running applications.
• Helidon 3 line: Build-tools documentation records a shift from a single version file to a version catalog for CLI archetype selection.
• Helidon 4: Official documentation introduces the virtual-thread-based Helidon WebServer, Project Nima, and Java 21 requirements.
• Package-manager era: The input package facts record Homebrew packaging of the `helidon` executable.

Related projects

• Helidon CLI is related to Helidon SE, Helidon MP, MicroProfile, Jakarta EE APIs, Maven archetypes, GraalVM Native Image, Project Loom virtual threads, and the Helidon build-tools repository that houses the CLI and Maven plugin work.

Sources

• https://github.com/helidon-io/helidon
• https://github.com/helidon-io/helidon-build-tools
• https://helidon.io/docs/latest/about/cli
• https://helidon.io/docs/v2/about/02_introduction
• https://helidon.io/docs/v4/about/intro
• https://helidon.io/nima
• https://raw.githubusercontent.com/helidon-io/helidon-build-tools/master/README.md
• https://raw.githubusercontent.com/helidon-io/helidon-build-tools/master/cli/README.md