Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of " eclipse.ini"
m (→-vm value: Windows Example) |
|||
(42 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | + | = Overview = | |
− | <code>eclipse.ini</code> | + | Eclipse startup is controlled by the options in <code>$ECLIPSE_HOME/eclipse.ini</code>. If <code>$ECLIPSE_HOME</code> is not defined, the default <code>eclipse.ini</code> in your Eclipse installation directory (or in the case of Mac, the <code>Eclipse.app/Contents/MacOS</code> directory) is used. |
− | + | ||
− | + | ||
− | + | ||
− | + | <code>eclipse.ini</code> is a text file containing command-line options that are added to the command line used when Eclipse is started up. There are many options available, please see [http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/runtime-options.html here]. | |
− | + | '''''Important:''''' | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | #'''''Each option and each argument to an option must be on its own line.''''' | |
+ | #'''''All lines after <code>-vmargs</code> are passed as arguments to the JVM, so all arguments and options for eclipse must be specified before <code>-vmargs</code> (just like when you use arguments on the command-line)''''' | ||
+ | #'''''Any use of <code>-vmargs</code> on the command-line replaces all <code>-vmargs</code> settings in the .ini file unless <code>--launcher.appendVmargs</code> is specified either in the .ini file or on the command-line. ([http://help.eclipse.org/juno/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fruntime-options.html&resultof=%22launcher%2eappendvmargs%22%20 doc])''''' | ||
+ | <br> | ||
− | + | By default, <code>eclipse.ini</code> looks something like this (the exact contents will vary based on operating system and which Eclipse package you have):<br> | |
+ | -startup | ||
+ | ../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar | ||
+ | --launcher.library | ||
+ | ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.100.v20110502 | ||
+ | -product | ||
+ | org.eclipse.epp.package.jee.product | ||
+ | --launcher.defaultAction | ||
+ | openFile | ||
-showsplash | -showsplash | ||
org.eclipse.platform | org.eclipse.platform | ||
--launcher.XXMaxPermSize | --launcher.XXMaxPermSize | ||
256m | 256m | ||
− | - | + | --launcher.defaultAction |
− | + | openFile | |
-vmargs | -vmargs | ||
+ | -Dosgi.requiredJavaVersion=1.5 | ||
+ | -XX:MaxPermSize=256m | ||
-Xms40m | -Xms40m | ||
-Xmx512m | -Xmx512m | ||
+ | |||
− | + | Among other things, this sets the heap space to 40MB initially and a maximum of 512MB, and also specifies a maximum PermGen size of 256MB. A max heap of 512MB might be OK for some users, but it's often necessary to bump that value up for large project sets or when some third-party plugins are installed. | |
+ | |||
+ | = Specifying the JVM = | ||
+ | |||
+ | One of the most recommended options to use is to [[FAQ How do I run Eclipse?#Find_the_JRE|specify a specific JVM]] for Eclipse to run on. Doing this ensures that you are ''absolutely certain'' which JVM Eclipse will run in and insulates you from system changes that can alter the "default" JVM for your system. Many a user has been tripped up because they thought they knew what JVM would be used by default, but they thought wrong. eclipse.ini lets you be '''CERTAIN'''. | ||
+ | |||
+ | The following examples of <code>eclipse.ini</code> demonstrate correct usage of the -vm option. | ||
+ | |||
+ | '''''Note the format of the -vm option - it is important to be exact''''': | ||
+ | |||
+ | *The -vm option and its value (the path) must be on separate lines. | ||
+ | *The value must be the full absolute or relative path to the Java executable, not just to the Java home directory. | ||
+ | *The -vm option must occur before the -vmargs option, since everything after -vmargs is passed directly to the JVM. | ||
+ | |||
+ | Here is an example of what <code>eclipse.ini</code> ''might'' look like on a Windows system after you've added the <code>-vm</code> argument and increased the maximum heap space: | ||
+ | <pre>-startup | ||
+ | plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar | ||
+ | --launcher.library | ||
+ | plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.100.v20110502 | ||
+ | -product | ||
+ | org.eclipse.epp.package.java.product | ||
+ | --launcher.defaultAction | ||
+ | openFile | ||
+ | --launcher.XXMaxPermSize | ||
+ | 256M | ||
+ | -showsplash | ||
+ | org.eclipse.platform | ||
+ | --launcher.XXMaxPermSize | ||
+ | 256m | ||
+ | --launcher.defaultAction | ||
+ | openFile | ||
+ | -vm | ||
+ | C:\Java\JDK\1.6\bin\javaw.exe | ||
+ | -vmargs | ||
+ | -Dosgi.requiredJavaVersion=1.5 | ||
+ | -Xms40m | ||
+ | -Xmx1024m | ||
+ | |||
+ | </pre> | ||
+ | Remember that the exact values will differ slightly depending on operating system and Eclipse package. | ||
+ | |||
+ | == -vm value: Windows Example == | ||
+ | |||
+ | This is how the <code>-vm</code> argument might look on Windows (your exact path to <code>javaw.exe</code> could be different, of course): | ||
− | |||
− | |||
− | |||
− | |||
-vm | -vm | ||
+ | C:\jdk1.7.0_21\bin\javaw.exe | ||
+ | |||
+ | An alternative way is to insert the following VM option before the -vmargs option in the Eclipse shortcut properties(edit the field Target inside the "Shortcut" tab): | ||
+ | |||
+ | -vm C:\jdk1.7.0_21\bin\javaw.exe | ||
+ | |||
+ | or | ||
+ | |||
+ | -vm C:\jdk1.7.0_21\jre\bin\java.exe | ||
+ | |||
+ | |||
+ | <br> This might not work on all systems. If you encounter "''Java was started but returned exit code=1''" error while starting the eclipse, modify the <code>-vm</code> argument to point to <code>jvm.dll</code> (exact path could be different): | ||
+ | |||
+ | -vm | ||
+ | C:\Development\Java\64bit\jdk1.7.0_09\jre\bin\server\jvm.dll | ||
+ | |||
+ | == -vm value: Linux Example == | ||
+ | |||
+ | This is how the -vm argument might look on Linux (your exact path to <code>java</code>could be different, of course): | ||
+ | |||
+ | -vm | ||
/opt/sun-jdk-1.6.0.02/bin/java | /opt/sun-jdk-1.6.0.02/bin/java | ||
− | |||
− | |||
− | |||
+ | == -vm value: Mac OS X Example == | ||
− | On a | + | On a '''Mac OS X''' system, you can find <code>eclipse.ini</code> by right-clicking (or Ctrl+click) on the Eclipse executable in Finder, choose Show Package Contents, and then locate <code>eclipse.ini</code> in the <code>MacOS</code> folder under <code>Contents</code>. |
− | + | To specify Java 6 for OS X: | |
− | + | ||
− | + | -vm | |
− | + | /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/bin/java | |
− | + | ||
− | /System/Library/Frameworks/JavaVM.framework/Versions/1. | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | For versions of Mac OS X 10.7+ the location has changed to | |
− | + | <pre>/Library/Java/JavaVirtualMachines/<''jdk_name_ver''>/Contents/Home/... | |
− | + | </pre> | |
+ | To be safer, determine the location for the JDK you intend to use via the utility /usr/libexec/java_home and put this value with .../bin/java appended into the Eclipse.ini file. | ||
+ | = See Also = | ||
− | + | *[[FAQ How do I run Eclipse?]] | |
− | *[[FAQ How do I run Eclipse?]] | + | *[[FAQ How do I increase the heap size available to Eclipse?]] |
− | *[[FAQ How do I increase the heap size available to Eclipse?]] | + | |
*[[FAQ How do I increase the permgen size available to Eclipse?]] | *[[FAQ How do I increase the permgen size available to Eclipse?]] | ||
{{Template:FAQ_Tagline}} | {{Template:FAQ_Tagline}} |
Latest revision as of 14:09, 8 August 2013
Contents
Overview
Eclipse startup is controlled by the options in $ECLIPSE_HOME/eclipse.ini
. If $ECLIPSE_HOME
is not defined, the default eclipse.ini
in your Eclipse installation directory (or in the case of Mac, the Eclipse.app/Contents/MacOS
directory) is used.
eclipse.ini
is a text file containing command-line options that are added to the command line used when Eclipse is started up. There are many options available, please see here.
Important:
- Each option and each argument to an option must be on its own line.
- All lines after
-vmargs
are passed as arguments to the JVM, so all arguments and options for eclipse must be specified before-vmargs
(just like when you use arguments on the command-line) - Any use of
-vmargs
on the command-line replaces all-vmargs
settings in the .ini file unless--launcher.appendVmargs
is specified either in the .ini file or on the command-line. (doc)
By default, eclipse.ini
looks something like this (the exact contents will vary based on operating system and which Eclipse package you have):
-startup ../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.100.v20110502 -product org.eclipse.epp.package.jee.product --launcher.defaultAction openFile -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vmargs -Dosgi.requiredJavaVersion=1.5 -XX:MaxPermSize=256m -Xms40m -Xmx512m
Among other things, this sets the heap space to 40MB initially and a maximum of 512MB, and also specifies a maximum PermGen size of 256MB. A max heap of 512MB might be OK for some users, but it's often necessary to bump that value up for large project sets or when some third-party plugins are installed.
Specifying the JVM
One of the most recommended options to use is to specify a specific JVM for Eclipse to run on. Doing this ensures that you are absolutely certain which JVM Eclipse will run in and insulates you from system changes that can alter the "default" JVM for your system. Many a user has been tripped up because they thought they knew what JVM would be used by default, but they thought wrong. eclipse.ini lets you be CERTAIN.
The following examples of eclipse.ini
demonstrate correct usage of the -vm option.
Note the format of the -vm option - it is important to be exact:
- The -vm option and its value (the path) must be on separate lines.
- The value must be the full absolute or relative path to the Java executable, not just to the Java home directory.
- The -vm option must occur before the -vmargs option, since everything after -vmargs is passed directly to the JVM.
Here is an example of what eclipse.ini
might look like on a Windows system after you've added the -vm
argument and increased the maximum heap space:
-startup plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.100.v20110502 -product org.eclipse.epp.package.java.product --launcher.defaultAction openFile --launcher.XXMaxPermSize 256M -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vm C:\Java\JDK\1.6\bin\javaw.exe -vmargs -Dosgi.requiredJavaVersion=1.5 -Xms40m -Xmx1024m
Remember that the exact values will differ slightly depending on operating system and Eclipse package.
-vm value: Windows Example
This is how the -vm
argument might look on Windows (your exact path to javaw.exe
could be different, of course):
-vm C:\jdk1.7.0_21\bin\javaw.exe
An alternative way is to insert the following VM option before the -vmargs option in the Eclipse shortcut properties(edit the field Target inside the "Shortcut" tab):
-vm C:\jdk1.7.0_21\bin\javaw.exe
or
-vm C:\jdk1.7.0_21\jre\bin\java.exe
This might not work on all systems. If you encounter "Java was started but returned exit code=1" error while starting the eclipse, modify the -vm
argument to point to jvm.dll
(exact path could be different):
-vm C:\Development\Java\64bit\jdk1.7.0_09\jre\bin\server\jvm.dll
-vm value: Linux Example
This is how the -vm argument might look on Linux (your exact path to java
could be different, of course):
-vm /opt/sun-jdk-1.6.0.02/bin/java
-vm value: Mac OS X Example
On a Mac OS X system, you can find eclipse.ini
by right-clicking (or Ctrl+click) on the Eclipse executable in Finder, choose Show Package Contents, and then locate eclipse.ini
in the MacOS
folder under Contents
.
To specify Java 6 for OS X:
-vm /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/bin/java
For versions of Mac OS X 10.7+ the location has changed to
/Library/Java/JavaVirtualMachines/<''jdk_name_ver''>/Contents/Home/...
To be safer, determine the location for the JDK you intend to use via the utility /usr/libexec/java_home and put this value with .../bin/java appended into the Eclipse.ini file.
See Also
- FAQ How do I run Eclipse?
- FAQ How do I increase the heap size available to Eclipse?
- FAQ How do I increase the permgen size available to Eclipse?
This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.