-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Windows: Create link after upgrade or use fix path for each mayor version #600
Comments
adipiciu
added a commit
to adipiciu/adoptium_installer
that referenced
this issue
Jan 7, 2024
Signed-off-by: adipiciu <[email protected]>
adipiciu
added a commit
to adipiciu/adoptium_installer
that referenced
this issue
Jan 7, 2024
Signed-off-by: adipiciu <[email protected]>
adipiciu
added a commit
to adipiciu/adoptium_installer
that referenced
this issue
Jan 7, 2024
Changed INSTALLDIR to fixed path to fix adoptium#422 and adoptium#600
adipiciu
added a commit
to adipiciu/adoptium_installer
that referenced
this issue
Jan 7, 2024
Signed-off-by: adipiciu <[email protected]>
Okeanos
pushed a commit
to Okeanos/adoptium-installer
that referenced
this issue
Aug 23, 2024
Signed-off-by: adipiciu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The path to the JDK changes after each upgrade. So you have to set all paths again after each upgrade and restart the applications.
Currently I use mklink on Windows to create a unique path for each Java version. But this step has to be done manually after each upgrade. This is very annoying, if the frustration becomes too much for some I fear that the installer will simply be removed and security will suffer.
Can you please just use a fixed path for a Java major version or link from a fixed path to the new version after each upgrade?
I am a developer and use multiple Java versions at the same time, so it doesn't help me if the installer sets the environment variables. The new variables would only be active after a restart of the development environment and I would still have to manually select the correct Java version in each project.
The text was updated successfully, but these errors were encountered: