Upgrade changes install location to default (with winget upgrade --exact --id EclipseAdoptium.Temurin.22.JR)
- Dominant language
- Jinja
- Stars
- 168
- Forks
- 77
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 12
Description
### Please provide a brief summary of the bug
Upgrade outdated version that was installed not in default directory cleans custom installation directory and installs upgrade to another directory
### Did you test with the latest update version?
- [X] Yes
### Please provide steps to reproduce where possible
1. Install outdated JRE v22 with `winget install --force --exact --id "EclipseAdoptium.Temurin.22.JRE" --override "INSTALLDIR=\"C:\Something\BlablablaPathForJRE22\""`
2. When found that JRE is outdated (with `winget upgrade`) start upgrade with `winget upgrade --exact --id EclipseAdoptium.Temurin.22.JRE`
3. Upgrade kills installation in C:\Something\BlablablaPathForJRE22\ and installs to Program Files... 👎 👎 :
### Expected Results
Expected that original installation path will be left as is!
### Actual Results
Upgrade outdated version that was installed not in default directory cleans custom installation directory and installs upgrade to another directory
### What Java Version are you using?
22.0.1+8 -> 22.0.2.9
### What is your operating system and platform?
Windows 10 22h2 x64
### How did you install Java?
`winget install --force --exact --id "EclipseAdoptium.Temurin.22.JRE" --override "INSTALLDIR=\"C:\Something\BlablablaPathForJRE22\""`
### Did it work before?
_No response_
### Did you test with other Java versions?
_No response_
### Relevant log output
_No response_
Contributor guide
Research direction
Reproduce the Windows 10 x64 case using the listed winget install and upgrade commands, including the custom INSTALLDIR path. Start by examining the installer scripts and the upgrade flow; done means upgrading Temurin JRE 22 preserves the original custom installation directory instead of removing it and installing under Program Files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100