I'm not sure when that started to happen (can be a few days ago) but suddenly my JAVA_HOME is set to 1.8 although I use 11 almost everywhere. I'm on Mac OS X. I certainly have such 11 set in my shell and even in the OS environment it seems (e.g. HelloWorld run in Intellij IDEA reports 11). I use jenv to manage java home and event set it in /Library/LaunchDaemons/setenv.java.plist

Spacemacs has a .env file that contains the env variables and values it „sees“. These are not the ones you set in your shell.

I still not get the rationale for this „feature“.

Hm, I had two values there; delete them but still no change.

It seems that I need to start the GUI app from the terminal...

@U06BE1L6T first SPC f e C-e, then SPC f e e - check if JAVA_HOME is there

It is!

I think it used to work properly with jenv - e.g. when I ran the repl in a directory where jenv local version was 1.8 it used 1.8. For other projects it used 11

then try adding it manually to exec-path-from-shell-variables

have you played with graal? graal can fubar java

some time ago

I actually think I might have executed force-init-spacemacs-env accidentaly in the past

then in emacs open eshell and type which java

before that it was working ok I think

make sure it’s pointing to the version you want

Hm, still doesn't work as expected. It's setting duplicate JAVA_HOME values. Maybe I need to do this somewhere in emacs config:

echo 'eval "$(jenv init -)"'

This is what I have in my /etc/profile:

eval "$(jenv init -)"
  eval "$(jenv enable-plugin export)"

No luck, very frustrating 😞. It used to work just fine - proper java version was picked up as per jenv settings (as in terminal).

It sounds like you have different Java settings between shell and login shell. I.e a terminal has one setting and gui apps have another

That might be true since it's notoriously hard to set this in Mac OS, but at least InteliJ IDEA seems to have the right setting

I'm using this jenv thing and its exporter plugin and also setting it in /Library/LaunchDaemons/setenv.java.plist

~/.spacemacs.env

I checked that and also deleted the JAVA_HOME occurences

At this point, I have no idea where the emacs app is getting its' env...

You could rename the .spacemacs.env and try to find out what would happen.

I did it and I think spacemacs automatically re-created it

will try one more time

Yes, the same thing again

So, basically, it uses the wrong JDK?

Yes

But now I kept that file and just removed all the content and it's at least using the proper global JDK (11)

but it still doesn't work with "local versions" that is for projects that have different java set locally with jenv (like 1.8)

Have you looked at section 11 of http://develop.spacemacs.org/doc/DOCUMENTATION.html

it seems I need to do this trick with:

eval "$(jenv init -)"
  eval "$(jenv enable-plugin export)"

does anyone know how to do that?

@U05254DQM not yet, will check it

Looks like the section 11.2 can be somewhat helpful

I'm now trying the latest develop version. It's been a long while since I updated it the last

After removing JAVA_HOME related stuff from .spacemacs.env, removing everything from various .plist files (/Library/LaunchDaemons/setenv.java.plist, /.MacOSX/environment.plist, /Library/LaunchAgents/environment.plist) and restarting my computer a couple of times it finally works as before! Thanks everyone for your help

I also added the jenv init code (see above) to .bash_profile but not sure if that had any effect at all.

Oh my, what a ride… 😐

Yeah, kind of unexpected 3 hours spent on this thing 😈