Transfer from: http://beansoft.blogchina.com/blog/article_10442.637044.html
Including the English version and Chinese version, especially needs to be worth mentioning that the -nl parameter can specify the language used when the program is started. For example: Eclipse -nl en_us will start the English language, this feature is installed international It is especially useful after the language package, which can be easily switched from the versions of each language. Note that IBM WSAD V5.1 also supports this feature.
Run Eclipse
After installing the Eclipse driver (unzip) into a directory (for example, C: / Eclipse), start the "workbencture" by running the Eclipse executable executable in the top-level installation directory. On the Windows system, the executable is called Eclipse.exe, and it is called Eclipse on the Linux system. Note: The following discussion describes the settings on the Windows system. The settings on Linux are similar.
If you are not specified, the platform creates the default workspace directory as a brother directory (for example, C: / Eclipse / Workspace). This workspace directory uses the default content area of the project, and is also used to save any required metadata. To perform shared installation or multi-workspace installation, it should be clearly indicated by the position of the work area rather than using the default value. There are two ways to control work area position: use the current working directory or use the -Data command line from variables.
Set the workspace location to within the current working directory
In this scenario, the work area location will be a directory called Workspace in the current working directory.
The easiest way to achieve this may use the following steps to create shortcuts:
Navigate to Eclipse.exe in the Windows Explorer and use Right-click to create a shortcut for Eclipse.exe. Edit the properties of the shortcut to enable the startup position: field identifies the parent directory of the workspace location (for example, C: / Users / Robert). Close the property dialog box and double-click the shortcut (if the directory provided is C: / Users / Robert, the workspace location will be C: / Users / Robert / Workspace).
Of course, you can also use the command prompt (by switching the directory to the workspace parent directory and then run Eclipse.exe) to get the same effect.
Use -DATA to set the specific location of the workspace
To use the -Data command lines, simply add -Data your_workspace_location to the target field or explicitly incorporated it on the command line.
Use -VM to set Java VM
It is recommended to explicitly specify which Java VM to use when running Eclipse. This can be achieved using the -vm command line (eg, -VM C: /JRE/bin/javaw.exe). If you do not use -VM, Eclipse will use a Java VM found on the O / S path. When other products are installed, they can change your path, causing another Java VM when the Eclipse is started next time.
Senior topic running in Eclipse
The Eclipse executable and platform itself provides many execution options that are interested in developing or debug Eclipse components. The general format running the Eclipse executable is:
Eclipse [Platform Options] [-VMargs [java vm arguments]]]
Eclipse startup parameters
command
description
Cause -Arch Architecture defines the processor architecture that the Eclipse platform runs thereon. The Eclipse platform typically calculates the best settings using the common value of the Java OS.Arch property. This is the value used by the Eclipse platform if this item is specified here. The value specified here can be used as a bootloader.getosarch () for the plugin. The sample values are: "X86", "SPARC", "PA-RISC" and "PPC". 2.0-Application ApplicationID To run the application. The application is declared by plugins that extends to org.eclipse.core.runtime.Applications extension points. This argument is usually required. If this item is specified, the value overwrites the value provided. If this item is not specified, the "Eclipse Workbench" will be run. 1.0-boot bootjarurl (recommended not to use; replaced with -configuration; support 1.0 compatibility). The position of the boot.jar of the Eclipse platform is represented as a URL. If this item is specified, it will be used to set the class path for the class loader that is loaded into the Eclipse platform boot the program class. It is only necessary to change the relative position of Startup.jar and Boot.jar. Note that the relative URL is not allowed. * 1.0-ClassLoaderProperties [file] If specified, use the type of device device attribute with a given position to activate the platform class type loader enhancement. The file index can be a file path or URL. Note that the relative URL is not allowed. Click here to get more details. 2.0.2-Configuration ConfigurationFileRLipse The location of the platform configuration file is represented as a URL. The configuration file determines the location of the Eclipse platform, the available plug-in set, and the main features. Note that the relative URL is not allowed. The configuration file is written to this location when installing or updating the Eclipse platform. 2.0-consOLELOG The error log mirror of the Eclipse platform is used to the console used to run the Eclipse. It is easy to use when combined with the -debug. 1.0-Data WorkspacePath To run the path of the workspace of the Eclipse platform. The work area location is also the default location of the project. The relative path is explained relative to the directory from which the Eclipse is started. 1.0-debug [optionsfile] places the platform in debug mode and loads the debug option (if specified) from the files at a given position. This file indicates which adjustments can be used for plugins and whether they have enabled. If the file location is not given, the platform finds a file called ".Options" in the directory of the Eclipse. URL and file system paths can be used as file locations. 1.0-dev [classpathentries] places the platform in the development method. Add the optional class path entry (a comma-separated list) to the runtime path of each plugin. For example, when the workspace contains the plug-in to be developed, specifying the -dev bin adds a class path entry for the directory of each plug-in project, allowing the latest generated class file. Remove redundant or non-existential path entries. 1.0-EndSplash Params is used to turn off the internal options of the flash screen at the Eclipse platform. This option has different grammar and semantics in different locations in the flash processing chain. 2.0-Feature FeatureID identifier of the main functional components. The main functional components provide product personality for Eclipse's lapse, and determine the product custom information used. 2.0-Keyring KeyringFilePath Disk Location The location of the database (or "key ring" file). This self-variable must be used in conjunction with the -password option.
The relative path is explained relative to the directory from which the Eclipse is started. 1.0-NL local defines the name of the language environment that the Eclipse platform is running. The Eclipse platform typically automatically calculates the best settings. This is the value used by the Eclipse platform if this item is specified here. The values specified here can be used as bootloader.getnl () for plugins. The sample values are: "en_us" and "fr_fr_euro". 2.0-NolazyregistryCacheLoading Cancel Activate Load Optimized Platform Registry Cache. By default, the extended configuration element is loaded from the registry cache (available) only when needed to reduce the memory occupation. This option will force the registry cache when it is started at startup. 2.1-NoreGistryCache bypass the read and write internal plug-in registry cache file. 2.0-Nosplash run the platform without the flash screen. 1.0-os operatingSystem defined Eclipse platform is running on its operating system. The Eclipse platform typically calculates the best settings using the common value of the Java OS.Name property. This is the value used by the Eclipse platform if this item is specified here. The value specified here can be used as a bootloader.getos () for plugins and used to resolve the appearance of $ OS $ variables in the plug-in list file. The sample values are: "Win32", "Linux", "HPUX", "Solaris", and "AIX". 1.0-Password Password authorized database password. Use the -keyring option. 1.0-Perspective PerspectiveID The perspective map is opened in the active table window when starting. If this parameter is not specified, the perspective view of the event is turned on. 1.0-PlugIncustomization PropertiesFile contains the location of the attribute file that is default the settings for the plugin preference. These default settings override the default settings specified in the primary features. The relative path is explained relative to the directory from which the Eclipse is started. 2.0-Plugins PluginsFileURL (recommended is not used; replaced with -configuration; support 1.0 compatibility). Specifies the location of the file of the Eclipse platform to find the plugin, indicating as a URL. This file is the properties file format, where the key is any user-defined name, the value is a prominent path to the Plugin.xml file or the path to the path to the directory containing the plugin. Note that the relative URL is not allowed. If this item is specified, this option will result in an appropriate temporary configuration. * 1.0-refresh starts the overall refresh option for the workspace when starting. This will make any changes made in the file system since the last platform. 1.0-showLocation Options for displaying the location of the workspace in the window title bar. In the release 2.0, this option is only used with the -Data command line from variables. 2.0-showSplash Params is used to display the internal options of the flash screen (executed by the executable Eclipse platform launcher). This option has different grammar and semantics in different locations in the flash processing chain. 2.0-VM VMPath To run the "Java Runtime Environment" (JRE) of the Eclipse platform. If this item is not specified, JRE is in JRE (it is a brothers directory of Eclipse executable). The relative path is explained relative to the directory from which the Eclipse is started. 1.0-WS Windowsystem Defines the Windows system that the Eclipse platform is running. The Eclipse platform typically calculates the best settings using the common value of the Java OS.Name property. This is the value used by the Eclipse platform if this item is specified here.
The values specified here can be used as bootloader.getws () for plugins, configured to configure SWT and the occurrence of $ WS $ variables in the plug-in list file. The sample values are: "Win32", "Motif" and "GTK". 1.0 All independent variables (but not -VMargs) behind the -VMargs entry (but not -VMargs) are used as virtual machine (i.e., the front of the class to be run) to the indicated Java VM. Note: If Eclipse is booted (for example, -data) provided after the Java VM argument (-VMargs), Eclipse will not start and you will receive an error that "JVM is terminated. Export code is 1".
Run on different VMs
Run Eclipse on J9
When running Eclipse on the J9 version 1.5, the following VM option is recommended:
Eclipse.exe [Eclipse Arguments] -VM PATH_TO_J9W.EXE -VMARGS -MS: 32 -MM: 2048 -MO: 32768 -Moi: 32768-MCA: 32 -MCO: 128 -MX: 2000000
When running Eclipse on J9 2.0, the default auto variable selected by J9W should be the appropriate option. However, to override the Eclipse executable to automatically set the parameters internally, you must specify -VMargs without any parameters, as shown below:
Eclipse.exe [eclipse arguments] -VM PATH_TO_J9W.EXE -VMARGS
For further information, refer to J9 VM documents and help.
Run Eclipse on IBM Developer Kit, Java (TM) Technology Edition VM
IBM Developer Kit, Java (TM) Technology Edition 1.3 Linux default VM settings are suitable for initial research work, but is not enough when making large development. For large development, VM arguments should be modified to make more stacks available. For example, the following settings will allow Java heaps to increase by 256MB:
-VMargs -xmx256m
Running Eclipse
After you install (unzip) the Eclipse driver in a directory. (Such as c: / eclipse), start the Workbench by running the Eclipse executable file found in the top level install directory The executable file is called eclipse.exe on Windows systems and Eclipse on Linux Systems. Note: The Following Discussion Describes Setting Up on Windows Systems. Setup on Linux is analogous.
If you do not specify otherwise, the platform creates a default workspace directory as a sibling of the executable. (For example, c: / eclipse / workspace) This workspace directory is used as the default content area for your projects as well as holding for . any required metadata For shared or multi-workspace installs you should explicitly state the location of your workspace rather than using the default There are two ways to control the location of your workspace:. using the current working directory or using the -data command line Argument.Setting The Workspace location to be inside the capital Working Directory
In this Scenario, The Workspace Location Will Be A Directory Called Workspace Inside The Current Working Directory.
Perhaps the Easiest Way of doing this is to create a shortcut using the folowing steps:
Navigate to eclipse.exe in the Windows Explorer and using a right button drag, create a shortcut to eclipse.exe Edit the properties of the shortcut such that the Start in:. Field identifies the parent directory of your workspace location (for example, c : / users / robert). Close The Properties Dialog and Double-Click on The Shortcut (IF The Provided Directory Was C: / Users / Robert, The Workspace Location Would Be C: / Users / Robert / Workspace).
.
Setting a Specific Location for the Workspace with -data
To use the -data command line argument, simply add -data your_workspace_location (for example, -data c: / users / robert / myworkspace) to the Target field in the shortcut properties, or include it explicitly on your command line.
Setting the java vm using -vm
IT is Recommended That You Explicitly Specify Which Java VM To Use WHEN Running Eclipse. This is achieved with the --vm command line argument (for example, -vm c: /j/bin/javaw.exe). If you don't use -vm, Eclipse will use the first Java VM found on the O / S path. When you install other products, they may change your path, resulting in a different Java VM being used when you next launch Eclipse.Advanced Topics in Running Eclipse
The Eclipse Executable and The Platform Itself Offer A Number of Execution Options of Interest To People Developing or Debugging Parts of Eclipse. The General Form of Running The Eclipse Executable IS:
Eclipse [Platform Options] [-VMargs [java vm arguments]]]
Eclipse Startup Parameters
Command
Description
Since-arch architectureDefines the processor architecture on which the Eclipse platform is running. The Eclipse platform ordinarily computes the optimal setting using the prevailing value of Java os.arch property. If specified here, this is the value that the Eclipse platform uses. The value specified here is available to plug-ins as BootLoader.getOSArch () Example values:. "x86", "sparc", "PA-RISC", "ppc" .2.0-application applicationIdThe application to run Applications are declared by plug-. ins supplying extensions to the org.eclipse.core.runtime.applications extension point. This argument is typically not needed. If specified, the value overrides the value supplied by the configuration. If not specified, the Eclipse Workbench is run.1.0-boot BootjarURL (deprecated; replaced by -configuration; supported for 1.0 compatibility). The location of the eclipse platform '
s boot plug-in code (boot.jar), expressed as a URL. If specified, it is used to set the classpath for the class loader that loads the Eclipse platform bootstrap class loader. Only required when changing the relative location of startup. jar and boot.jar. Note that relative URLs are not allowed. * 1.0-classloaderproperties [file] Activates platform class loader enhancements using the class loader properties file at the given location, if specified. The file argument can be either a file path or a URL. Note that relative URLs are not allowed. Click here for more details.2.0.2-configuration configurationFileURLThe location for the Eclipse Platform configuration file, expressed as a URL. The configuration file determines the location of the Eclipse platform, the set of available plug-ins, and the primary feature. Note relative URLs are not allowed. The configuration file is written to this location when the Eclipse platform is installed or updated. 2.0-consolelogMirrors the Eclipse platf that orm's error log to the console used to run Eclipse. Handy when combined with -debug.1.0-data workspacePathThe path of the workspace on which to run the Eclipse platform. The workspace location is also the default location for projects. Relative paths are interpreted relative to the directory that Eclipse was started from.1.0-debug [optionsFile] Puts the platform in debug mode and loads the debug options from the file at the given location, if specified. This file indicates which debug points are available for a plug-in And WHETHER or NOT THEY Are Enabled. if a file location is not given, The Platform Looks in The Directory That Eclipse Was Started from for a file caled ".options"
. Both URLs and file system paths are allowed as file locations. 1.0-dev [classpathEntries] Puts the platform in development mode. The optional classpath entries (a comma separated list) are added to the runtime classpath of each plug-in. For example , when the workspace contains plug-ins being developed, specifying -dev bin adds a classpath entry for each plug-in project's directory named bin, allowing freshly generated class files to be found there. Redundant or non-existent classpath entries are eliminated.1.0 -endsplash paramsInternal option for taking down the splash screen when the Eclipse platform is up and running. This option has different syntax and semantics at various points along the splash screen processing chain.2.0-feature featureIdThe ID of the primary feature. The primary feature gives THE LAUNCHED Instance of Eclipse Its Product Personality, and Determines The Product Customization Information Used.2.0-Keyring KeyringFilePaththe Location of The Authorization Database (O O r "key ring" file) on disk. This argument must be used in conjunction with the -password option. Relative paths are interpreted relative to the directory that Eclipse was started from.1.0-nl localeDefines the name of the locale on which the Eclipse platform is running The Eclipse platform ordinarily computes the optimal setting automatically If specified here, this is the value that the Eclipse platform uses The value specified here is available to plug-ins as BootLoader.getNL () Example values:.... "en_US "and" fr_fr_euro ".2.0-NolazyregistryCacheLoadingDeactiVates Platform Plug-in registry cache loading optimization. by Default, Extensions'
configuration elements will be loaded from the registry cache (when available) only on demand, reducing memory footprint. This option will force the registry cache to be fully loaded at startup.2.1-noregistrycacheBypasses the reading and writing of an internal plug-in registry cache file.2.0-nosplashRuns the platform without putting up the splash screen.1.0-os operatingSystemDefines the operating system on which the Eclipse platform is running. The Eclipse platform ordinarily computes the optimal setting using the prevailing value of Java os.name property. If specified here, this is the value that the Eclipse platform uses. The value specified here is available to plug-ins as BootLoader.getOS (), and used to resolve occurrences of the $ os $ variable in paths mentioned in the plug-in manifest file "Win32", "Linux", "HPUX", "Solaris", "AIX" .1.0-password passwordthe password for the authorization database. Used in conjunction with the-keyring option.1.0-inpective personpec tiveIdThe perspective to open in the active workbench window on startup. If this parameter is not specified, the perspective that was active on shutdown will be opened.1.0-plugincustomization propertiesFileThe location of a properties file containing default settings for plug-in preferences. These default settings override default settings specified in the primary feature relative paths are interpreted relative to the directory that eclipse was started from.2.0-plugins pluginsFileURL (Deprecated;. replaced by -configuration;
supported for 1.0 compatibility). The location of the file that specifies where the Eclipse platform finds plug-ins, expressed as a URL. The file is in property file format where the keys are arbitrary user defined names and the values are comma separated lists of either explicit paths to plugin.xml files, or paths to directories containing plug-ins. Note that relative URLs are not allowed. If specified, this option causes the creation of a suitable temporary configuration. * 1.0-refresh Option for performing a global refresh of the workspace on startup. This will reconcile any changes that were made in the file system since the platform was last run. 1.0-showlocation Option for displaying the location of the workspace in the window title bar. in release 2.0 this option only worked in Conjunction with the -data command line argument.2.0-showsplash paramsinternal option for Showing The Splash Screen (Done By The Executable Eclipse Platform Launcher). This Option Has DiffERENT SYNTAX AND S emantics at various points along the splash screen processing chain.2.0-vm vmPathThe location of Java Runtime Environment (JRE) to use to run the Eclipse platform. If not specified, the JRE is at jre, sibling of the Eclipse executable. Relative paths are interpreted relative to the directory that eclipse was started from.1.0-ws windowSystemDefines the window system on which the Eclipse platform is running. The Eclipse platform ordinarily computes the optimal setting using the prevailing value of Java os.name property. If specified here, this Is The Value That The Eclipse Platform Uses. The value specified here is available to plug-ins as bootloader.
getWS (), used to configure SWT, and used to resolve occurrences of the $ ws $ variable in paths mentioned in the plug-in manifest file Example values:. "win32", "motif", "gtk" .1.0All arguments following (but not including) the -vmargs entry are passed directly through to the indicated Java VM as virtual machine arguments (that is, before the class to run) Note:. If an Eclipse startup argument, such as -data, is provided after the Java VM Arguments (-VMargs), Eclipse Will NOT Start and You Will Receive A "JVM TERMINATED. EXIT CODE = 1" error.
Running on Different VMS
Running Eclipse On J9
WHEN Running Eclipse On J9 Version 1.5, IT is Recommended That You Use The Following VM Options:
Eclipse.exe [Eclipse Arguments] -VM PATH_TO_J9W.EXE -VMARGS -MS: 32 -MM: 2048 -MO: 32768 -Moi: 32768-MCA: 32 -MCO: 128 -MX: 2000000
. When running Eclipse on J9 version 2.0, the default arguments chosen by J9W should be suitable However, to override the parameters which are automatically set internally by the Eclipse executable, you must specify -vmargs with no following arguments as follows:
Eclipse.exe [eclipse arguments] -VM PATH_TO_J9W.EXE -VMARGS
Please refer to the J9 VM Documentation and help for further information.
Running Eclipse on the IBM Developer Kit, Java (TM) Technology Edition VM
The default VM settings for IBM Developer Kit, Java (TM) Technology Edition 1.3 Linux work well for initial exploration, but are not sufficient for large scale development. For large scale development you should modify your VM arguments to make more heap available. For example , The Following Setting Will Allow The Java Heap To Grow To 256MB:
-VMargs -xmx256m
Author Blog:
http://blog.9cbs.net/fishbob21/
related articles
PicoContainer-TWO Minute Tutorial PicoContainer-One Minute Description Eclipse Running Command Line Parameters Based on the Eclipse3.0.x Configuring Struts-based Web Development Environment By developing a Struts project experience
