-
Notifications
You must be signed in to change notification settings - Fork 394
Trouble Shooting
Barnesly edited this page Dec 3, 2025
·
8 revisions
If, when running jenv doctor, you see
[ERROR] Java binary in path is not in the jenv shims.
[ERROR] Please check your path, or try using /path/to/java/home is not a valid path to java installation.make sure export JENV_ROOT=/usr/local/opt/jenv appears before if which jenv > /dev/null; then eval "$(jenv init -)"; fi in .bash_profile.
This is related to symlinks the next issue.
- Start by enabling symlinks issue below.
- After symlinks has been enabled. In Git Bash navigate to jenv location. Default is
~/.jenv - Enable symlinks for the repository
git config core.symlinks true - Do a new checkout of
bin/jenvrungit checkout -- bin/jenv
Your problems should be solved.
Symlinks aren't working https://stackoverflow.com/a/40914277
It seems that it becomes a full copy instead of a symlink ~/.jenv/versions should have a size of 0, but without symlinks this grows fast since each alias is a full copy of the JVM.
- You need to run Git Bash as administrator (can be configure to always run as administrator under Properties -> Compatibility, make sure you know what this means).
- In Git Bash run
export MSYS=winsymlinks:nativestrictthis could be added to ~/.bash_profile