Skip to content Skip to sidebar Skip to footer

Why Does Sbt Report "no Java Installations Was Detected" With $java_home Set?

I have 2 sbt-android-scala projects. The first one is a single one: $ ls -al drwxr-xr-x 13 alex staff 442 Dec 24 20:44 . drwxr-xr-x 4 alex staff 136 Dec 24 21:08 .. drwxr-

Solution 1:

I had it failing for completely different reason: I had GREP_OPTIONS="--color=always" so sbt couldn't properly determine my Java version (it's piping grep output to sed and so on). Removing GREP_OPTIONS from my environment solved the issue.

Solution 2:

I think you should get the root authority if your ${JAVA_HOME} is configured in root path.such as /root/java/jdk.

Solution 3:

I just had the same issue appear out of nowhere. When I executed java -version, the following error was returned:

Error occurred during initialization ofVMCould not reserve enough space forobject heap

It turned out that Eclipse was consuming all of the available memory and that I could not start another JVM. Thus, I exited Eclipse, and everything works, fine.

Solution 4:

I just ran into the same problem on Ubuntu. In my case, it was caused by a setting in my JAVA_TOOL_OPTIONS:

JAVA_TOOL_OPTIONS=-Djavax.net.ssl.trustStore=

Solution 5:

I tried to install java again and apt told me to do a --fix-broken, and that solved the issue with out need to re-install java: sudo apt --fix-broken install

Post a Comment for "Why Does Sbt Report "no Java Installations Was Detected" With $java_home Set?"