fetch-jdk doesn't store the arch in the directory name, so different architectures get confused
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 205
- Forks
- 129
- PR merge metrics
- No merged PRs in 30d
Description
For example /Users/chrisseaton/.mx/jdks/labsjdk-ce-11-jvmci-22.1-b03/ is that AMD64 or AArch64?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the fetch-jdk command and trace how it constructs directories under ~/.mx/jdks. Reproduce the case with JDKs for different architectures and inspect the resulting paths. Done means the directory names distinguish AMD64 from AArch64 so fetch-jdk cannot confuse them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100