jenv VS asdf

https://github.com/jenv/jenv to switch among multiple Java versions

I would recommend https://www.jenv.be/

Look at the https://www.jenv.be/ configure section and add the Java location where Homebrew installed your java. If I remember correctly, it should be somewhere in /usr/local/Cellar/openjdk/**

On my case I prefer use jenv (which is available on aur)

You might like jenv

There are a handful of different ways to temporarily swap out Java versions. In this case, you could probably edit the start scripts to point directly to the path for the Java version you want to use (instead of just "java" which is most likely referring to the most recent). I was already using jEnv for other things, so I configured it so JRE 1.6 would be used in my Nullpomino directory, and the latest JRE would be used everywhere else.

I like jenv for that. You can have a java version set per-project, systemwide, shell session, etc.

I don’t know if this is the “correct” way, but if you are Unix based I would recommend jenv. This is a Java environment manager, similar to pyenv if you know it. Using this tool you can easily switch from one installed version to another. It makes managing Java versions a bliss.

Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions

https://asdf-vm.com/

Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?

These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…

We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).

(asdf)[https://asdf-vm.com/] fully supports Python and almost any other language. I've been using it for Ruby, Python, Elixir, and other languages for years and never looked back.

Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).

There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:

I've really been enjoying asdf, which is a program that allows you to install specified versions of dev utilities as well as dynamically manage them via shims and .tool-versions files.

I use the asdf version manager.

You might check out rtx[1]

Its an asdf[2] rewrite, in rust, that can do most of the things nvm can

[1] https://github.com/jdx/rtx

[2] https://github.com/asdf-vm/asdf