Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Management #386

Open
kmbarlow opened this issue Jan 26, 2023 · 1 comment
Open

Version Management #386

kmbarlow opened this issue Jan 26, 2023 · 1 comment

Comments

@kmbarlow
Copy link

I am wondering if it would be possible to have an option to update the chain on the add algorithm. When a new incremental version of java comes out and we add it (e.g. 17.0.6), if there is an existing mapping for the root (e.g 17 -> 17.0.2), the mapping will persist and not be updated to the newer 17.0.6.

jenv add /usr/local/Cellar/openjdk@17/17.0.6/ openjdk64-17.0.6 added 17.0.6 added 17.0 already present, skip installation 17.0.6 already present, skip installation

I'd like an option to specify that the root should be updated so that they always point at latest of that release.

@stoerr
Copy link

stoerr commented May 16, 2024

Right, and if one is removing obsolete versions, the now broken links like 17 / 17.0 in the example aren't removed but still block the installation of the new JDK as those versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants