Reputation: 4533

Maven not picking JAVA_HOME correctly

I am on windows environment and using maven to compile my project. Although I just created the project and added the dependencies for various libararies.

As I added them maven started complaining for the missing tools.jar, so i added below to my pom.xml:

<dependency>
  <groupId>com.sun</groupId>
  <artifactId>tools</artifactId>
  <version>1.6</version>
  <scope>system</scope>
  <systemPath>${java.home}/../lib/tools.jar</systemPath>
</dependency>

When i ran the maven install, i got an error for the missing jar as below :

[ERROR] Failed to execute goal on project GApp: Could not resolve dependencies for project GApp:GApp:war:0.0.1-SNAPSHOT: Could not find artifact com.sun:tools:jar:1.6 at specified path C:\Program Files\Java\jre6\lib\tools.jar -> [Help 1]

The issue is that the tools.jar is in "C:\Program Files\Java\jdk1.6.0_26\lib" and is correctly set in the JAVA_HOME environment variable but the maven is still looking in jre folder as in error message "C:\Program Files\Java\jre6\lib\tools.jar".

C:\>echo %JAVA_HOME%
C:\Program Files\Java\jdk1.6.0_26

Interestingly: when i set the full path in dependency, it worked just fine. But i don't want to hard code it.

<dependency>
  <groupId>com.sun</groupId>
  <artifactId>tools</artifactId>
  <version>1.6</version>
  <scope>system</scope>
  <systemPath>C:\Program Files\Java\jdk1.6.0_26\lib\tools.jar</systemPath>
</dependency>

Can someone suggest any dynamic solution for this?

Upvotes: 35

Answers (10)

Carlos Eduardo Gorges

Reputation: 41

it's just a bug in maven support for eclipse. You can ignore this error for now.

The support for local dependencies will be discontinued in near future, I think the maven developers understand this approach is not the best way to resolve this, but we know that exists some proprietary jars (like db2's JDBC driver license) that never will resided in a public repository ...

Upvotes: 0

Victor

Reputation: 3475

Check to see if you have a .mavenrc file, it may be forcing JAVA_HOME to be something other that what is set in the environment variable.

Upvotes: 0

Vijay Kumar

Reputation: 2707

Also look in the .mavenrc file in your home dir. This caught me off guard.

I changed everything as suggested only to find that my .mavenrc file set the JAVA_HOME to an older version.

Upvotes: 1

Luke Hutchison

Reputation: 9190

You might be using the wrong Maven installation. Switch it in Window > Preferences > Maven > Installations. I had mine set to the Fedora Maven install; changing it back to the default (the version embedded in m2e) fixed the problem for me.

I suspect what was causing this issue is that the Fedora Maven install was using Fedora's OpenJDK, which probably puts tools.jar in a weird location (everything about Fedora's OpenJDK is weird and non-standard), so Maven can't find it.

Upvotes: 1

rustyx

Reputation: 85266

It's a bug in the Eclipse Maven support. Eclipse doesn't support all of the global Maven properties as per the Maven specs.

According to the specs:

${java.home} specifies the path to the current JRE_HOME environment use with relative paths to get for example

At least in Eclipse 4.3.1 that is not the case, here java.home always points to the JRE that was used to launch Eclipse, not the build JRE.

To fix the issue you need to start Eclipse using the JRE from the JDK by adding something like this to eclipse.ini (before -vmargs!):

-vm
C:/<your_path_to_jdk170>/jre/bin/server/jvm.dll

Upvotes: 39

Alejandro

Reputation: 21

Maven ${java.home} property is set and taken from different places depending your Eclipse execution:

from the default JRE selected for the workspace

Window>Preferences>Java>Installed JREs
from the specific Eclipse project,

Java Build Path>Libraries>JRE System Library
from the Run configuration.

Run Configurations> Specific Run Configuration > JRE

Remember your JRE home paths points to a JDK or JRE under JDK

Upvotes: 2

gordy

Reputation: 9786

When you add the JAVA_HOME environment variable, if there are spaces in the path you must wrap the whole thing in quotes.

Upvotes: 1

Manfred Moser

Reputation: 29912

You should NEVER use system scope dependencies. All the code in tools.jar will be available just via the running JVM already. You should remove this dependency altogether..

Also in order to check what runtime Maven is using just call

mvn -v

If you are still having a dependency to the tools jar as a problem, one of the dependencies you added has that dependency (and it is really bad quality). To find out which one it is run