We Keep Coding

OSX Maven issues after homebrew maven opgrade

Immediately after I upgraded my Mac from maven 3.6.0 to 3.6.3 with homebrew, I was no longer able to build my maven project. I've been through torrents of version dependency problems, etc, but I'm hoping to avoid stepping through any more of that stuff than I need to. And before I continue, I wanted to bounce this off of you guys to see if it indicates anything ominous, or if it's ops normal (since I've never paid too much attention to it in the past.) In question is the variance in java version numbers between mvn --version and java -version, i.e., 1.8.0_191 vs 14.0.1:
$ java -version java version "1.8.0_191" Java(TM) SE Runtime
Environment (build 1.8.0_191-b12) Java HotSpot(TM) 64-Bit Server VM
(build 25.191-b12, mixed mode)
mvn --version Apache Maven 3.6.3
(cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home:
/usr/local/Cellar/maven/3.6.3_1/libexec Java version: 14.0.1, vendor:
N/A, runtime:
/usr/local/Cellar/openjdk/14.0.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x",
version: "10.15.6", arch: "x86_64", family: "mac"
Thanks in advance!

Turns out my JAVA_HOME variable somehow evaporated in the homebrew upgrade. Once I set that, all 12 million problems disappeared instantly. Thanks for the comment khmarbaise!

Maven Java home configuration

I installed JDK and set up Maven. Call of mvn -version i get returns:
The JAVA_HOME environment variable is not defined correctly This environment variable is needed to run this program NB: JAVA_HOME should point to a JDK not a JRE
$JAVA_HOME variable is set to C:\Program Files\Java\jdk1.8.0_131\bin in system variables.
Call of %JAVA_HOME% returns path C:\Program Files\Java\jdk1.8.0_131\bin.
Where is the problem?

As you can see in the documentation the JAVA_HOME variable must point to the java installation path, not to the bin folder.
Change it to C:\Program Files\Java\jdk1.8.0_131

The question is about Windows but I came here trying to solve the problem on Ubuntu.
I faced a similar problem. I configured $JAVA_HOME in /etc/environment
like $JAVA_HOME=PATH_TO_JDK for example $JAVA_HOME=/home/max/jdk1.8.0_144
Careful with
White space after path declaration $JAVA_HOME=/home/max/jdk1.8.0_144[[_NO_WHITE_SPACE_AFTER_DECLARATION]]
Don't put any double apostrophe $JAVA_HOME="/home/max/jdk1.8.0_144"
Don't put /bin e.g $JAVA_HOME=/home/max/jdk1.8.0_144/bin <- This is wrong

Yes, original question is about pure windows, but for those who came here wondering about windows linux subsystem WSL, I stumbled across the thing trying to set up my win WSL, to use windows java Open jdk binaries. Though in a while i gave up on that idea. Installed jdk with 'sudo apt install ...' and then set WSL java home from installed path:
root#mypc://# java -version
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (build 1.8.0_265-8u265-b01-0+deb9u1-b01)
OpenJDK 64-Bit Server VM (build 25.265-b01, mixed mode)
root#mypc://# which java
/usr/bin/java
root#mypc://# realpath /usr/bin/java
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
use yours realpath instead.
root#mypc://# export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
root#mypc://# mvn -v
Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117; 2019-08-27T15:06:16Z)
Maven home: /mnt/c/javaDir/mvn/apache-maven-3.6.2
Java version: 1.8.0_265, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-43-microsoft", arch: "amd64", family: "unix"
add export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 to a ~/.bash_profile for this being set every time linux subsystem is lunched.

JDK Version Not in Allowed Range

I'm using Mule CE 3.7, who uses Maven to compile it's project.
The problem is, when is compiling, he returns this error:
[ERROR] Detected JDK Version: 1.8.0-60 is not in the allowed range [1.7,1.8].
I already did all the solutions that i found, JAVA_HOME and PATH are configured.
If i run Java commands, they return me this:
MBP-de-axz:~ axz$ java -version
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
MBP-de-axz:~ axz$ javac -version
javac 1.8.0_60
MBP-de-axz:~ axz$ mvn -version
Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T08:57:37-03:00)
Maven home: /usr/local/Cellar/maven/3.3.3/libexec
Java version: 1.8.0_60, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_60.jdk/Contents/Home/jre
Default locale: pt_BR, platform encoding: UTF-8
OS name: "mac os x", version: "10.10.1", arch: "x86_64", family: "mac"
I already configured the Pom file of my project like this:
<requireJavaVersion>
<version>[1.7,1.9)</version>
</requireJavaVersion>
So all is pointing to the same Java version.
And this is happening in my Mac and Windows.
The project only works if i change to Java 1.7, but i can use 1.7 because one of my libraries uses Java 1.8.
Anyone have an ideia of what could it be ?
Thanks !

You probably want to use [1.7,1.9) as version range. This means it accept version between 1.7 (inclusive) until 1.9 (exclusive). Since 1.8.0_60 is bigger than 1.8, it was out of range with the previous version range. Btw, [1.8) would both include and exclude 1.8, so that shouldn't work.

This error happens, when the maven JDK version and PROJECT JDK version doesn't match.
Inorder to fix that, try to find out the mvn jdk version first using
"mvn --version"
Then set the desired JDK version using set JAVA_HOME="c:\jdk_location_here". If you re-run the "mvn --version". You will see the updated JDK Version there.Now try to run your build.
Long term: Set the JAVA_HOME in environment variables.

The problem is that Mule is not compatible yet with JDK 1.8, i need to use JDK 1.7
I should have read the requeriments.

Unsupported major.minor version 52.0 on HikariDataSource

I have Windows 7 and I am using maven to compile my codes on command line. About 2 days ago, I had Java 6 SDK installed and that's what I was using to compile my codes. Everything was working fine; the compiled war file would start on its own after tcserver is launched. Yesterday, due to some other issue, I had to install Java 8 SDK. This is when my problem started.
It turned out that the installation of Java 8 introduced some other problem. So, I uninstalled Java 8 and rebooted. After that, I could still compile my codes. However, when I go to my tcserver manager and click Start on the process, I would get an error in the log file saying something about "Unsupported major.minor version 52.0". After some researches, it appears to be a problem with Java 8. But I did uninstall Java 8. To make sure that I have Java 6 SDK installed, I uninstalled the Java 6 SDK, re-installed it, and then re-compile my codes. That did not help and the log still shows the same error.
My mvn -v returns the followings,
Maven home: C:\installs\maven3\apache-maven-3.1.1
Java version: 1.6.0_45, vendor: Sun Microsystems Inc.
Java home: C:\installs\Java\jdk1.6.0_45\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
My echo %JAVA_HOME% returns the followings,
C:\installs\Java\jdk1.6.0_45
My java -version returns the followings,
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
From what I can see, the version of Java that is being used in compiling my codes appears to be 6. Why am I still getting that Hikari error? Where else do I need to fix to correct the problem?

You should do the following steps:
First delete your local maven repository (usually in /.m2/repository).
This would delete all installed jar-files (which may have been created with your JDK8)
call mvn clean (to clean all your files in the target directory
Check your %JDK_HOME% (may be it points to your JDK-8
Rebuild your project by mvn package
But:
1.6.0_45, vendor: Sun Microsystems Inc.
This is really bad out-dated. You should update at least to Java7. There are unclosed security-issues in this version.

Detected JDK Version: 1.6.0-24 is not in the allowed range 1.7

When I ran the command
mvn clean package
I am getting error:
Detected JDK Version: 1.6.0-24 is not in the allowed range 1.7.
How to fix the above error? I tried to check jdk version isntalled and got this
java version "1.7.0_03"
Java(TM) SE Runtime Environment (build 1.7.0_03-b04)
Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode)
how to fix this?

Normally when execute the mvn -v you may see something like
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da;
2013-02-19 20:51:28+0700)
Maven home: C:\Java.Application\Apache\apache-maven-3.0.5\bin\..
Java version: 1.7.0_15, vendor: Oracle Corporation
Java home: C:\Java.Application\Sun\Java\jdk1.7.0_15\jre
Default locale: en_US, platform encoding: MS874
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
If the result point to the JDK Version: 1.6.0-24 or other than your expect. Please simply set the JAVA_HOME to your JDK Version: 1.7.0_03 instead.
I hope this may help.

Make sure that your environment (PATH) is set up to use the JDK version that you want to use for compiling. You can check this by running the following in the shell or command window where you want to run Maven:
java -version
javac -version
Make sure that both java and javac are pointing to the correct version. It's possible that you have a 1.7 JRE (which does not include the compiler) and a 1.6 JDK (which includes the compiler) and the wrong one is being used.
If necessary, adjust your JAVA_HOME and PATH environment variables.
Just noticed that you're on CentOS - it's possible that java and javac point to different versions. Use the alternatives command to check that, see here for an example: http://wiki.centos.org/HowTos/JavaRuntimeEnvironment - you will have to check both the java and the javac command.

Check your JRE System Library in Eclipse. Does it show jdk1.6.0-24?
For me I had to right click the JRE System Library and go to Build Path -> Configure Build Path, in the Libraries tab I had to click JRE System Library and edit it. I set it to the Workspace Default JRE, which for me is jdk1.7.0_80 (not sure why it wasn't set to that already).