# Install jenv with Homebrew, MacPorts, pacman, scoop Manage your Java environment. Version 0.6.0 via Homebrew; verified from local package data. Also installable with pacman: sudo pacman -S jenv. ## Install ```sh sudo av install brew:jenv ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install jenv ``` Evidence: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install jenv ``` Evidence: MacPorts ports tree: java/jenv/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ### Linux - pacman (92%): ```sh sudo pacman -S jenv ``` Evidence: Arch Linux sync databases: jenv from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ### Windows - Scoop (92%): ```sh scoop install extras/jenv ``` Evidence: Scoop official bucket manifest trees: bucket/jenv.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:jenv - **Package manager:** Homebrew - **Version:** 0.6.0 - **Source summary:** Manage your Java environment - **Homepage:** - **Repository:** - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - jenv (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.6.0 ## Project history and usage jenv is a shell-oriented Java environment manager. Its README describes it as an updated fork of jenv adapted from rbenv, focused on switching Java versions and setting JAVA_HOME at global, directory-local, or per-shell scope without installing Java itself. ### Project history The public GitHub repository for jenv was created in 2013. The project documentation names Gildas Cuisinier as maintainer and frames the repository as a continuation of an earlier beloved Java environment manager rather than a from-scratch package installer. The release stream visible on GitHub shows a compact Unix shell tool that continued to receive maintenance releases through the 0.5.x and 0.6.x series. Release notes for 0.6.0 include fixes around shim behavior, shell support, install instructions, and the addition of a command for selecting a Java version for one command invocation. ### Adoption history jenv became useful in Java shops because the JDK landscape is fragmented: Android, server, build, and legacy projects often require different Java majors on the same developer machine. Its README explicitly calls out Android tools using Java 8 while server applications use later releases, which explains its fit with project-local version files. Homebrew, MacPorts, pacman, and Scoop package metadata in the input show that jenv escaped a single-source install workflow and became a cross-package-manager convenience for developers who already install JDKs through their platform tooling. ### How it is used A typical jenv workflow is to install the shell hooks, add already-installed JDK homes with `jenv add`, enable the export plugin when JAVA_HOME management is desired, and use `jenv global`, `jenv local`, or `jenv shell` to select the active version. `jenv local` writes a `.java-version` file in the working tree. ### Why package nerds care jenv matters to package-manager users because it deliberately does less than SDKMAN-style installers: it manages shims and environment selection, while Homebrew or the operating system installs Java. That separation makes it a small glue package with outsized value on machines that carry several vendor and versioned JDKs. ### Timeline - 2013: Public GitHub repository created for jenv/jenv. - 2020: GitHub release 0.5.3 appears in the release stream. - 2025: GitHub release 0.6.0 records shim, install, and shell-support maintenance. ### Related projects - The README explicitly traces jenv's style to rbenv. It also sits beside Homebrew, MacPorts, SDKMAN-style Java installers, and vendor OpenJDK packages rather than replacing them. ### Sources - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## 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: ./.java-version ## Other Package-Manager Records - pacman - jenv - 0.6.0-1: normalized package name match | Arch Linux sync databases: jenv from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Manage your Java environment | https://github.com/jenv/jenv - MacPorts - jenv: normalized package name match | MacPorts ports tree: java/jenv/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 - Scoop - extras/jenv: normalized package name match | Scoop official bucket manifest trees: bucket/jenv.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/jenv.yml](https://github.com/mxcl/pkgdb/blob/main/combined/jenv.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