Eclipse Startup Parameters

From Network

Eclipse Startup parameter-clean2013- .- - Ten: -Introduction to eclipse startup parameters, such as when adding a plug-in, if it is not displayed, use Eclipse-clean boot) In fact, Eclipse is a system that can be configured very flexibly, and in addition to starting in the default way, you can specify various parameters to customize the startup mode. After referencing some of the information, I summed up some of the more commonly used start-up command Arguments, if there is an incorrect place for you to point out. -Arch [processor architecture] Description: Specifies the class example of the processor used: Eclipse-arch x86 or Eclipse-Arch SPARC-Application Description: Specifies the app to run, Example of plug-in ID plus extension ID for an extended org.eclipse.core.applications extension point ID: for example, with a plug-in ID of Edu.sdu.app and an extension ID of MyApp, Eclipse-application Edu.sdu.app.myapp, your extended application will be executed.-Clean Description: Empty plugin Cache Content Example: Eclipse-Clean , sometimes the plugin does not show up because eclipse caches the plug-in to speed up the boot process, and if specified this parameter empties the cache and loads it from the beginning-Configuration [Cofigfile Location] Description: Specifies the position of the configuration file, starting with the profile Config.ini under this directory to launch an example: Eclipse-configuration d:/eclipse/Configuration-data [Workspace Location] Description: Specifies an example of workspace position at startup: for example, the workspace position is located at D:/myworkspace, then Eclipse-data d:/Myworkspace-Debug [option file] Description: Start Eclipse in Debug state, all debug switches specified in the. Options file Example: Eclipse-debug d:/eclipse/. Options-Dev [classpath entry] Description: Starts eclipse as a development state, which adds all the specified paths as an example of classpath for each plug-in: For example, Eclipse-Dev Bin, which loads all classes generated in the bin directory into the classpath, which is useful when developing plug-ins-Nosplash Description: Specifies that splash screen is not displayed at startup example: Eclipse-Nosplash-VM [JRE Path] Description: Specifies an example of the Java Virtual machine used at startup: for example, to use its own Java Virtual machine, the Eclipse-vmd:/j2sdk1.4.2_04/jre/bin/java.exe, this also has the advantage that can open a console, can display the console information, of course, if use ECLIPSE-VM d:/j2sdk1.4.2_04/jre/bin/Javaw.exe will no longer display the console-Vmargs [Java VM arguments] Description: Specifies an example of the Java Virtual machine parameter to be used at startup: for example, to specify the amount of memory used, the Eclipse-vmargs"-xms256m-xmx1024m"NOTE: This parameter must be placed on the last side of all parameter variables if you think your eclipse is slow to start (say more than 20 seconds), maybe you need to tweak your eclipse startup parameters, here are some tips"':1. Check the JVM settings that started eclipse. In help\about Eclipse sdk\configuration detail, you can see the JVM that started eclipse. This JVM is different from the installed JDK you set up in Eclipse. If the JVM or JDK that started eclipse1.4, it's best to change to JDK5, because JDK 5 has better performance than 1.4. C:\eclipse\eclipse.exe-vm"C:\Program files\java\jdk1.5.0_08\ Bin\javaw.exe"2. Check the size of the heap used by eclipse. There is a profile Eclipse.ini under the C:\eclipse directory, which configures the default heap size for Eclipse startup-Vmargs-xms40m-xmx256m So you can change the default value to:-Vmargs-xms256m-xmx512m Of course, you can also do this by changing the size of the heap to- +. C:\eclipse\eclipse.exe-vm"C:\Program files\java\jdk1.5.0_08\ Bin\javaw.exe"-vmargs-xms256m-xmx512m3. Other startup parameters. If you have a dual-core CPU, you might be able to try this parameter:-xx:+USEPARALLELGC allows the GC to execute faster. (only the newly added parameters to the GC in JDK 5) are transferred from http://hi.baidu.com/dd_taiyangxue/item/bde49535c3d4d7be633aff51

From official website!

-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>-console [port] (OSGi) equivalent to setting Osgi.console to [port].-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 emptystringTo simply enable debug (i.e.,ifThe Options File location isNot specified)-Dev [entries] (OSGi) equivalent to setting Osgi.dev to [entries] or the emptystringTo simply enable dev mode (i.e.,ifentries is not specified)-eclipse.keyring <file path>(Equinox) Set toOverrideLocation of thedefaultSecure Storage-eclipse.password <file path>(Equinox) If specified, the secure storage treats contents of the file asAdefaultPassword. When notSet, password providers is 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 is refreshed. Any user/plug-inchDefined configuration data isNot purged. No Application isRun, any product specifications is ignored and no UI ispresented (e.g., the splash screen isNot drawn)-install <location>(Main) equivalent to setting Osgi.install.area to<location>--launcher.defaultaction <option>(executable) specifies thedefaultAction to take when the launcher isStarted without any"-"Arguments on the command line. Currently the only supported value is "OpenFile". The"OpenFile"Option tells the launcher thatifIt isCalled with a command line this only contains arguments that DoNot start with"-", then those arguments should is treated as ifThey followed"--launcher.openfile". Eclipse Myfile.txtthis isThe kind of command line the launcher would receive on Windows if youDoubleClick a file that isassociated with eclipse, or youSelectand choose"Open with"Or"Send to"Eclipse.--launcher.openfile <space separated list of files>(executable) a space separated list of files to pass to the application. This option isTypically used to pass a list of files to being opened by an Eclipse application. This option requires SWTinchOrder to fire the necessary swt_opendocEvent  forThe files that is specified. Relative paths is resolved first against the current working directory, and second against the Eclipse program direct Ory.--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 would look forA file beside the launcher with the same name and the extension. ini. (ie Eclipse.exe looks forEclipse.ini, Product.exe looks forProduct.ini)--launcher.suppresserrors (executable) If specified the executable won't display any error or message dialogs. this isUsefulifThe executable isBeing usedinchAn unattended situation.--launcher.secondthread (executable) MacOSX Onlyif specified the executable would create the Java VM on a secondary thre  Ad. This should usedifA swing application isBeing run. SWT won't workif  ThisOption isspecified.--launcher.timeout <value>(executable) a timeout value forHowLongThe launcher should spend trying to communicate with a already running eclipse before the launcher gives up and launches ANewEclipse instance. Default is  -(seconds).--launcher. Xxmaxpermsize <value>(executable) If specified, and the executable detects that the VM being used isA Sun VM, then the launcher would automatically add the-xx:maxpermsize=<value> VM argument. The executable isNot capable of detecting Sun VMs on all platforms.--Launcher.appendvmargs (executable) If specified, any VMS arguments on the commandline would be appended to any VM Argumen TS specifiedinchThe launcher. ini file. Using ThisOption isRecommendedinchEvery launcher. ini file that specifies VM arguments, because thedefaultBehavior of overriding VMS arguments can have unexpected side-effects.--Launcher.overridevmargs (executable) If specified on the commandline, overrides the effect of--launcher.appendvmargsinchA launcher. ini file such that none of the VM argumentsinchThe. ini file is considered asSoon asA-vmargs option isdetected on the commandline.-name <string>The name to be displayedinchThe Task bar item forThe splash screen is the application starts up (not applicable on Windows). Also used asThe title of the error dialogs opened by the launcher. When notSet, the name isThe 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 isshown-os <operating system>(OSGi) equivalent to setting Osgi.os to<operating system>-plugincustomization <location>(Runtime) equivalent to setting eclipse.plugincustomization to<location>-product <id>(OSGi) equivalent to setting eclipse.product to<id>-registrymultilanguage (Runtime) equivalent to setting Eclipse.registry.MultiLanguage to"true"-showsplash <bitmap>(executable, Main) specifies the bitmap to useinchThe splash screen.  If specified, the launcher is able to show the splash-screen before starting the Java VM. If not specified, Main would find the bitmapusingThe osgi.splashlocation and Osgi.splashpath properties.-startup <location>(executable) The location of the jar used to startup eclipse. The jar referred to should has the Main-class attributeSetTo Org.eclipse.equinox.launcher.Main. If ThisParameter isNotSet, the executable would lookinchThe Plugins directory forTheorg.eclipse.equinox.launcher Bundle with the highest version.-user <location>(OSGi) equivalent to setting Osgi.user.area to&LT;LOCATION&GT;-VM <path to Java vm>(executable, Main) when passed to the Eclipse executable, ThisOption isUsed to locate the Java VM to use to run Eclipse. It should is the full file system path to an Appropriate:java jre/bin directory, Java executable, Java shared library (JV  M.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 anyEvent, the executable then passes the path to the actual VMS used to Java MainusingTHE-VM argument. Java Main then stores ThisValueinchECLIPSE.VM.-vmargs [vmargs*] (executable, Main) when passed to the Eclipse, ThisOption isUsed to customize the operation of the Java VMs to use to run Eclipse. If specified, Thisoption must come at the end of the command line. EvenifNot specified on the executable command line, the executable would automatically add the relevant arguments (including theclassBeing launched) to the command line passed into JavausingThe-vmargs argument. Java Main then stores ThisValueinchEclipse.vmargs.-ws <window system>(OSGi) equivalent to setting osgi.ws to<window system>

Can see, or the official website of the good, in the future to help the document or find the official website of the good!

Eclipse Startup Parameters