Tony Evans wrote:Also how do you get around the windows program file problem, all JDKS are stored there but eclipse does not like spaces. so C:\Program file\java is seen as C:\Program.
It also does not like "C:\Program file\java".
Jeremy Goodell wrote: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
Jaikiran Pai wrote:
Tony Evans wrote:Also how do you get around the windows program file problem, all JDKS are stored there but eclipse does not like spaces. so C:\Program file\java is seen as C:\Program.
It also does not like "C:\Program file\java".
It's always recommended not to install Java (or any Java related utilities) in a folder containing a space in its path. It's better to move the Java installation outside the Program Files and then set the JAVA_HOME appropriately to point to the new path. For example, I have JDK 5 at C:/Java/jdk1.5.0
The m2eclipse plugin still says Eclipse is running in a jre
SCJP
G
G
Eclipse ignores the "-vm" parameter, if one is specified in its .ini file, if it finds a JRE installed in the "Program Files" directory.
If you can find a path with no obstacles, it probably doesn't lead anywhere
I have now religiously gone through all the above suggestions to no avail
Peter Johnson wrote:I see that you are running a 64-bit OS and using 64-bit Eclipse. I hope that your JDK is also 64-bit. If it is, then I don't see what the issue is,
Peter Johnson wrote:The key is that the -vm entry must come before the -vmargs entry. And the path to the JVM can be to java.exe, javaw.exe or jvm.dll. In either case what Eclipse is really looking for is the jvm.dll (or jvm.so on Linux) so that it can load it. I just point Eclipse directly to the jvm.dll.
Alister Ernest wrote:
Peter Johnson wrote:The key is that the -vm entry must come before the -vmargs entry. And the path to the JVM can be to java.exe, javaw.exe or jvm.dll. In either case what Eclipse is really looking for is the jvm.dll (or jvm.so on Linux) so that it can load it. I just point Eclipse directly to the jvm.dll.
This was the change that got my settings to work.
Thanks Peter.
Consider Paul's rocket mass heater. |