Eclipse Command line arguments
|
|
Listed below are the E
clipse command line arguments
processed by various parts of the Eclipse runtime. Many of these values can also be specified using
System properties
either on the command line using -D VM arguments, by specifying their values in a config.ini file or by using a
| Argument | Description |
|
-application�<id>
(Runtime) |
equivalent to setting eclipse.application to <id> |
|
-arch�<architecture>
(OSGi) |
equivalent to setting osgi.arch to
<architecture> |
| -clean (OSGi) | equivalent to setting osgi.clean to "true" |
-configuration
<location>(Main) |
equivalent to setting osgi.configuration.area to
<location> |
| equivalent to setting osgi.console to [port] or the empty string if the default port is to be used (i.e., when the port is not specified) | |
| -consoleLog (Runtime) | equivalent to setting eclipse.consoleLog to "true" |
-data
<location>(OSGi) |
equivalent to setting osgi.instance.area to
<location> |
| -debug [options file] (OSGi) | equivalent to setting osgi.debug to [options file] or the empty string to simply enable debug (i.e., if the options file location is not specified) |
| -dev [entries] (OSGi) | equivalent to setting osgi.dev to [entries] or the empty string to simply enable dev mode (i.e., if entries are not specified) |
-eclipse.keyring
<file path>(Equinox) |
Set to override location of the default secure storage |
-eclipse.password
<file path>(Equinox) |
If specified, the secure storage treats contents of the file as a default password. When not set, password providers are used to obtain a password. |
-feature
<feature id>(Runtime) |
equivalent to setting eclipse.product to
<feature id> |
-framework
<location>(Main) |
equivalent to setting osgi.framework to
<location> |
| -initialize (Main) | initializes the configuration being run. All runtime related data structures and caches are refreshed. Any user/plug-in defined configuration data is not purged. No application is run, any product specifications are ignored and no UI is presented (e.g., the splash screen is not drawn) |
-install
<location>(Main) |
equivalent to setting osgi.install.area to
<location> |
-keyring
<location>(Runtime) |
the location of the authorization database on disk. This argument has to be used together with the -password argument. |
--launcher.library
<location>(Executable) |
the location of the eclipse executable's companion shared library. If not specified the executable looks in the plugins directory for the appropriate org.eclipse.equinox.launcher.[platform] fragment with the highest version and uses the shared library named eclipse_* inside. |
--launcher.ini
<location>(Executable) |
the location of the product .ini file to use. If not specified the executable will look for a file beside the launcher with the same name and the extension .ini. (ie eclipse.exe looks for eclipse.ini , product.exe looks for product.ini) |
| --launcher.suppressErrors (Executable) | If specified the executable will not display any error or message dialogs. This is useful if the executable is being used in an unattended situation. |
| --launcher.secondThread (Executable) MACOSX ONLY | If specified the executable will create the Java VM on a secondary thread. This should used if a swing application is being run. SWT will NOT work if this option is specified. |
--launcher.XXMaxPermSize
<value>(Executable) |
If specified, and the executable detects that the VM being used is a Sun VM, then the launcher will automatically add the -XX:MaxPermSize=
<value>vm argument. The executable is not capable of detecting Sun VMs on all platforms. |
-name
<string> |
The name to be displayed in task bar item when the application starts up. When not set, the name is the name of the executable. |
-nl
<locale>(OSGi) |
equivalent to setting osgi.nl to
<locale> |
| -noExit (OSGi) | equivalent to setting osgi.noShutdown to "true" |
| -noLazyRegistryCacheLoading (Runtime) | equivalent to setting eclipse.noLazyRegistryCacheLoading to "true" |
| -noRegistryCache (Runtime) | equivalent to setting eclipse.noRegistryCache to "true" |
| -noSplash (Executable, Main) | controls whether or not the splash screen is shown |
-os
<operating system>(OSGi) |
equivalent to setting osgi.os to
<operating system> |
-password
<password>(Runtime) |
the password for the authorization database |
-pluginCustomization
<location>(Runtime) |
equivalent to setting eclipse.pluginCustomization to
<location> |
-product
<id>(OSGi) |
equivalent to setting eclipse.product to
<id> |
-showSplash
<bitmap>(Executable, Main) |
specifies the bitmap to use in the splash screen. If specified, the launcher may be able to show the splash screen before starting the Java VM. If not specified, Main will find the bitmap using the osgi.splashLocation and osgi.splashPath properties. |
-startup
<location>(Executable) |
The location of jar used to startup eclipse. The jar referred to should have the Main-Class attribute set to org.eclipse.equinox.launcher.Main. If this parameter is not set, the executable will look in the plugins directory for theorg.eclipse.equinox.launcher bundle with the highest version. |
-user
<location>(OSGi) |
equivalent to setting osgi.user.area to
<location> |
-vm
<path to java vm>(Executable, Main) |
when passed to the Eclipse executable, this option is used to locate the Java VM to use to run Eclipse. It should be the full file system path to an appropriate: Java jre/bin directory, Java Executable, Java shared library (jvm.dll or libjvm.so), or a Java VM Execution Environment description file. If not specified, the Eclipse executable uses a search algorithm to locate a suitable VM. In any event, the executable then passes the path to the actual VM used to Java Main using the -vm argument. Java Main then stores this value in eclipse.vm. �See Eclipse Memory Configuration |
| -vmargs [vmargs*] (Executable, Main) | |
-ws
<window system>(OSGi) |
equivalent to setting osgi.ws to
<window system> |