Specify JDK for Maven to use

Question

I am trying to build a Hudson plugin I ve modified and it requires jdk1 6  This is fine  but I don t see how I can tell maven where the different jdk is  I ve found few mentions on the internet but they don t seem to apply to me  Some suggest adding some config to  m2 settings xml but I don t have a settings xml  Plus  I don t want to use 1 6 for all maven builds    One kink is I am using mvn in cygwin  if that matters at all  It appears I should be able to make the specification in the project pom file  but the existing pom is pretty bare    So bottom line is  is there a way to specify a jdk for a single invocation of maven

User · Answer

You could also set the JDK for Maven in a file in your home directory ~/.mavenrc:

JAVA_HOME='/Library/Java/JavaVirtualMachines/jdk-11.0.5.jdk/Contents/Home'

This environment variable will be checked by the mvn script and used when present:

  if [ -f "$HOME/.mavenrc" ] ; then
    . "$HOME/.mavenrc"
  fi

https://github.com/CodeFX-org/mvn-java-9/tree/master/mavenrc

User · Answer

So bottom line is  is there a way to specify a jdk for a single invocation of maven    Temporarily change the value of your JAVA HOME environment variable

User · Answer

I know its an old thread  But I was having some issues with something similar to this in Maven for Java 8 compiler source  I figured this out with a quick fix mentioned in this article thought I can put it here and maybe can help others     lt properties gt       lt project build sourceEncoding gt UTF-8 lt  project build sourceEncoding gt       lt maven compiler source gt 1 8 lt  maven compiler source gt       lt maven compiler target gt 1 8 lt  maven compiler target gt   lt  properties gt

User · Answer

If you have installed Java through brew in Mac then chances are you will find your Java Home Directory here    Library Java JavaVirtualMachines adoptopenjdk-8 jdk Contents Home   The next step now would be to find which Java Home directory maven is pointing to  To find it type in the command   mvn -version     The fields we are interested in here is  Java version and runtime   Maven is currently pointing to Java 13  Also  you can see the Java Home path under the key runtime  which is    usr local Cellar openjdk 13 0 2 8 2 libexec openjdk jdk Contents Home   To change the Java version of the maven  we need to add the Java 8 home path to the JAVA HOME env variable   To do that we need to run the command   export JAVA HOME  Library Java JavaVirtualMachines adoptopenjdk-8 jdk Contents Home in the terminal   Now if we check the maven version  we can see that it is pointing to Java 8 now     The problem with this is if you check the maven version again in the new terminal  you will find that it is pointing to the Java 13  To avoid this I would suggest adding the JAVA HOME variable in the    profile file   This way whenever your terminal is loading it will take up the value you defined in the JAVA HOME by default  This is the line you need to add in the    profile file   export JAVA HOME  Library Java JavaVirtualMachines adoptopenjdk-8 jdk Contents Home   You can open up a new terminal and check the Maven version   mvn -version  and you will find it is pointing to the Java 8 this time

User · Answer

Using this command below also worked for me  using it right after installation of Java 8 from here https   www oracle com java technologies javase-downloads html export JAVA HOME    usr libexec java home

User · Answer

I  had  build  problem  with  maven  within  Eclipse on Windows 7    Though I  observed  mvn build  was  running  just  fine  from command  line   mvn -T 5 -B -e -X -U -P test clean install -Dmaven surefire debug  --settings       infra-scripts maven-conf settings xml    gt  output log   Eclipse  was  considering  as  default JVM a  JRE  installation  instead  of JDK  so  it  was  failing  on compilation   I  added to eclipse ini  following line   -vm C  Program Files  x86  Java jdk1 8 0 25 bin   Also  when  starting  from eclipse  I  used in  Goals   section following list   -T 5 -B -e -X -U -P test clean install -Dmaven surefire debug  --settings       infra-scripts maven-conf settings xml   Compilation error  got  solved

User · Answer

I say you setup the JAVA HOME environment variable like Pascal is saying  In Cygwin if you use bash as your shell should be   export JAVA HOME  cygdrive c pathtothejdk   It never harms to also prepend the java bin directory path to the PATH environment variable with   export PATH   JAVA HOME  bin   PATH    Also add maven-enforce-plugin to make sure the right JDK is used  This is a good practice for your pom    lt build gt    lt plugins gt      lt plugin gt         lt groupId gt org apache maven plugins lt  groupId gt         lt artifactId gt maven-enforcer-plugin lt  artifactId gt         lt executions gt           lt execution gt             lt id gt enforce-versions lt  id gt             lt goals gt               lt goal gt enforce lt  goal gt             lt  goals gt             lt configuration gt               lt rules gt                 lt requireJavaVersion gt                   lt version gt 1 6 lt  version gt                 lt  requireJavaVersion gt               lt  rules gt             lt  configuration gt           lt  execution gt         lt  executions gt       lt  plugin gt     lt  plugins gt   lt  build gt    Please  see Maven Enforcer plugin     Usage

User · Answer

As u said  Plus  I don t want to use 1 6 for all maven builds      So better I will say modify your pom file and specify which jdk version to use    lt build gt       lt plugins gt           lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-compiler-plugin lt  artifactId gt               lt version gt 3 7 0 lt  version gt               lt configuration gt                   lt source gt 1 9 lt  source gt                   lt target gt 1 9 lt  target gt               lt  configuration gt           lt  plugin gt       lt  plugins gt   lt  build gt    It will ensure that your particular project uses that version of jdk

User · Answer

compile compile has a user property that allows you to specify a path to the javac   Note that this user property only works when fork is true which is false by default     mvn -Dmaven compiler fork true -Dmaven compiler executable  path to the javac compile   You might have to double quote the value if it contains spaces    gt  mvn -Dmaven compiler fork true -Dmaven compiler executable  C      javac  compile   See also Maven custom properties precedence

User · Answer

For Java 9     lt build gt       lt plugins gt           lt plugin gt               lt artifactId gt maven-compiler-plugin lt  artifactId gt               lt version gt 3 7 0 lt  version gt               lt configuration gt                   lt source gt 9 lt  source gt                   lt target gt 9 lt  target gt               lt  configuration gt           lt  plugin gt       lt  plugins gt   lt  build gt

User · Answer

Hudson also allows you to define several Java runtimes  and let you invoke Maven with one of these   Have a closer look on the configuration page

User · Answer

Yet another alternative to manage multiple jdk versions is jEnv  After installation  you can simply change java version  locally  i e  for a specific project directory by   jenv local 1 6   This will also make mvn use that version locally  when you enable the mvn plugin   jenv enable-plugin maven

User · Answer

Maven uses variable  JAVACMD as the final java command  set it to where the java executable is will switch maven to different JDK

User · Answer

Seems that maven now gives a solution here   Compiling Sources Using A Different JDK  Let s say your JAVA HOME points to JDK7  which will run maven processes   Your pom xml could be      lt build gt       lt plugins gt           lt  -- we want JDK 1 6 source and binary compatiblility -- gt           lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-compiler-plugin lt  artifactId gt               lt configuration gt                   lt source gt 1 6 lt  source gt                   lt target gt 1 6 lt  target gt               lt  configuration gt           lt  plugin gt           lt  --     -- gt           lt  -- we want sources to be processed by a specific 1 6 javac -- gt           lt plugin gt               lt groupId gt org apache maven plugins lt  groupId gt               lt artifactId gt maven-compiler-plugin lt  artifactId gt               lt version gt 3 1 lt  version gt               lt configuration gt                 lt verbose gt true lt  verbose gt                 lt fork gt true lt  fork gt                 lt executable gt   JAVA 1 6 HOME  bin javac lt  executable gt                 lt compilerVersion gt 1 3 lt  compilerVersion gt               lt  configuration gt           lt  plugin gt       lt  plugins gt   lt  build gt    If your developpers just add  and customize  the following lines in their settings xml  your pom will be platform independant     lt settings gt             lt profiles gt                 lt profile gt         lt id gt compiler lt  id gt           lt properties gt             lt JAVA 1 4 HOME gt C  Program Files Java j2sdk1 4 2 09 lt  JAVA 1 4 HOME gt             lt JAVA 1 6 HOME gt C  Program Files Java j2sdk1 6 0 18 lt  JAVA 1 6 HOME gt           lt  properties gt       lt  profile gt     lt  profiles gt             lt activeProfiles gt       lt activeProfile gt compiler lt  activeProfile gt     lt  activeProfiles gt   lt  settings gt

[maven-2] Specify JDK for Maven to use

Examples related to maven-2

Examples related to settings

Examples related to java

Examples related to pom.xml