m2eclipse: Eclipse is running in a JRE, but a JDK is required

Question

I have a problem with m2eclipse (0.10.0) together with eclipse galileo (Build id: 20090920-1017).

I always get the error message:"Eclipse is running in a JRE, but a JDK is required". I have tried several things, but nothing works. The error message is still there. Here are the things I have tried:

• In Window>Preferences>Java>Installed JREs I checked JDK1.6.0_20. DOES NOT WORK

• In Window>Preferences>Java>Installed JREs I removed all JREs. Only the checked JDK1.6.0_20 is still there. DOES NOT WORK

• In Window>Preferences>Java>Installed JREs>Execution Environments I choosed JavaSE-1.6 and checked JDK1.6.0_20[perfect match]. DOES NOT WORK.

• In Preferences of the eclipse desktop start icon I added the -vm parameter (C:\\Programme\\eclipse_galileo\\eclipse\\eclipse.exe -vm C:\\Programme\\Java\\jdk1.6.0_20\\bin). DOES NOT WORK.

• I added the clean parameter (C:\\Programme\\eclipse_galileo\\eclipse\\eclipse.exe -vm C:\\Programme\\Java\\jdk1.6.0_20\\bin -clean). DOES NOT WORK.

• I added the -vm parameter to the eclipse.ini file with a carriage return after -vm and C:/Programme/Java/jdk1.6.0_20/bin/javaw.exe in a new line. DOES NOT WORK.

• After doing all these things I removed the m2eclipse plugin and installed it once again. DOES NOT WORK.

New ideas I have tried:

• In Preferences of the eclipse desktop start icon I put the executable at the end (C:\\Programme\\eclipse_galileo\\eclipse\\eclipse.exe -vm C:\\Programme\\Java\\jdk1.6.0_20\\bin\\javaw.exe). DOES NOT WORK.

• I changed in eclipse.ini the slashes to backslashes. DOES NOT WORK.

Here is my eclipse.ini file:

-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519
-product
org.eclipse.epp.package.jee.product
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vm
C:\Programme\Java\jdk1.6.0_20\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m

Is anyone out there who have other ideas? Any help is appreciated.

Thank You very much. GernoK

Answer 1

Unbelievable, the solution to this problem has nothing to do with slashes, backslashes, quotes, spaces, jre, jdk, jvm, javaw, ....

The answer is that you have to have a line break between

-vm

and the path.

So in the eclipse.ini file:

THIS WILL NOT WORK:

-vm C:\java\jdk\bin\javaw.exe

BUT THIS WILL:

-vm
C:\java\jdk\bin\javaw.exe

Answer 2

MARIO-ORTEGON answered is the right answer to this problem. The only thing you need to do is to move this line "-vm C:\\java\\jdk\\bin\\javaw.exe" under the section -product org.eclipse.epp.package.jee.product in eclipse.ini. like this: -product org.eclipse.epp.package.jee.product -vm C:\\java\\jdk\\bin\\javaw.exe save and restart the eclipse. Error will be gone.

Answer 3

I think these are answers needed when editing the eclipse.ini or STS.ini files:

A lot of people make these mistakes because they make certain assumptions (which is not correct):

1. Mistake #1: Writing the parameters in the same line . Unlike JVM command line, Eclipse expects every parameters to be placed in different line in its eclipse.ini file. One of the most common mistake is (which should be written in 2 separated lines):

   -vm c:/Java/jdk1.6.0_31/bin/javaw.exe

2. Mistake #2: Writing the -vm and -vmargs in the wrong order . Sequence does matter. The -vmargs has to be put before the -vm . Why? Because once the -vm has been specified, the VM will be fully specified and the rest of the -vmargs will be ignored.

3. Mistake #3: Assuming the eclipse.ini will stay the same if you don't change it . Some plugins installation may have auto configuration (which after restarting automagically change the eclipse.ini file, or other .ini config file, eg STS.ini if you are using SpringSource Tool Suite for example), they will append indiscriminately the -vm before the -vmargs . Check for double occurrence of -vm or -vmargs .

4. Mistake #4: Pointing to the path of JVM, instead of the binary when specifying -vm . Eclipse expects the Java JVM binary, not just the JAVA_HOME path eg -vm c:/Java/jdk1.6.0_31/bin/javaw.exe not just -vm c:/Java/jdk1.6.0_31

For the original question, it seems the Mistake #2 is the cause. Instead of the one, you should move the -vm to the end, after -vmargs :

-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519
-product
org.eclipse.epp.package.jee.product
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
-vm
C:\Programme\Java\jdk1.6.0_20\bin\javaw.exe

Answer 4

I had the same problem with Eclipse reporting that it was running in the JRE (Win7 x64, 32 Bit JDK 1.6 update 21), even though I was specifying that it should use the JDK.

I finally deleted JRE6 which is optionally installable with the JDK and the message disappeared.

Someone with a deeper understanding of Windows will have to explain why it does this, but it is apparently ignoring the eclipse.ini setting, as well as JAVA_HOME and starting eclipse in the JRE anyway.

My eclipse.ini:

-vm
C:/Java/jdk1.6.0_21/bin/javaw.exe
-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519
-product
org.eclipse.epp.package.jee.product
-nosplash
org.eclipse.platform
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms32m
-Xmx1024m
-Xss6m
-XX:PermSize=32m
-XX:MaxPermSize=256m
-XX:CompileThreshold=5
-XX:MaxGCPauseMillis=10
-XX:MaxHeapFreeRatio=70
-XX:+UseParallelGC
-XX:+AggressiveOpts
-Dcom.sun.management.jmxremote

JAVA_HOME

C:\Windows\system32>echo %JAVA_HOME%
C:\Java\jdk1.6.0_21

Answer 5

I think you have to explicity add the executable to the -vm argument:

C:\Programme\eclipse_galileo\eclipse\eclipse.exe -vm C:\Programme\Java\jdk1.6.0_20\bin\javaw

Regarding the ini file, it depends on the full contents. What does your ini file contains?

Answer 6

Put these lines at the beginning of the eclipse.ini file:

-vm
G:/dev/jdk1.6.0_19/bin/javaw.exe

Answer 7

I'm getting the same error message as soon as I remove these two lines

-vm
C:\Programme\Java\jdk1.6.0_10\bin\javaw.exe

from my eclipse.ini file. Maybe you should use backslashes in that eclipse.ini.

Answer 8

I too had this issue. This problem disappeared when I upgrade to Eclipse Indigo. So try with Higher version.

Answer 9

Check your Installed JRE setting of Eclipse. It should point to JDK rather than JRE. Though it is a JRE setup. Remember JDK contains JRE and when Maven runs it tries to find out JDK mostly tools.jar.

Answer 10

There are two JVMs involved here; the one that Eclipse is running in and the one (or more) that the different projects in your workspace run in. I think this message refers to the JVM that Eclipse is running in. So, the solution is not contained in the "Installed JREs" section within Eclipse. It's the JVM that's in your path within Windows.

Answer 11

Java may be finding its files using the JAVA_HOME environment variable. Try changing it to C:\\Programme\\Java\\jdk1.6.0_20

In Windows XP, this is under Control Panel, System, Advanced tab, Environment Variables button.

Answer 12

尝试添加此：

-vm E:\java\jdk1.6\jre\bin\client\jvm.dll

Answer 13

Uninstall the JRE leaving ONLY the JDK and private JRE behind. Run Eclipse, and it will immediately complain that it can't find a JRE or JDK (assuming the -vm option is missing or wrong in your ini).

Now put the -vm path to javaw in your ini file, save and Eclipse will now load the JDK.

I actually went ahead and uninstalled everything Java and then reinstalled JDK 6 leaving out the public JRE and the database portion of the install.

Answer 14

The uninstall method is the only thing that worked for me. No amount of -vm magic made it happen until I only had the JDK installed.

Answer 15

I had the same problem but solved it. Add the -vm option as the first line in your eclipse.ini file and it will work.