jEnv
5.6#25 in runtime version managersLinuxmacOS
VisitjEnv vs nvm
What both publish
| Fact | jEnv | nvm |
|---|---|---|
| Integrations | Optional plugins can export Java settings for Gradle, Maven, Ant, Leiningen, and sbt. | Documented integrations include Docker, Ansible, zsh plugins, bash completion and optional nvshim shims. |
| Project configuration | A local version setting creates a .java-version file that can be checked into Git for a project. | nvm can use an .nvmrc file to specify a Node.js version for a project, with shell snippets documented for automatic switching. |
| Purpose | jEnv is a command-line tool for managing Java environments and switching between Java versions. | nvm lets users install and use different Node.js versions from the command line. |
| Shell support | The documentation gives setup instructions for Bash, Zsh, and Fish shells. | It works on POSIX-compliant shells including sh, dash, ksh, zsh, and bash. |
| Support | The site directs users to GitHub to report bugs or request missing features. | The project states that only the latest nvm version is supported. |
jEnv plans
No prices published.
nvm plans
- nvmFree
Pick jEnv if…
You want what its maker publishes above — check its page for the details.
Pick nvm if…
nvm suits developers who need to manage Node.js versions from the command line, including per-project version selection and CI/CD use. It is intended for per-user, per-shell installation.