Eclipse startup parameter configuration [Reproduced]

Document directory

• Set the workspace location to the current working directory
• Use-data to set a specific workspace location
• Use-VM to set Java VM
• Run eclipse on j9
• Run eclipse on IBM developer kit, Java (TM) technology edition VM

Eclipse.exe-vmargs-xverify: None-XX: + useparallelgc-XX: permsize = 20 m-xms64m-xmx256m

Set the workspace location to the current working directory

In this solution, the workspace location is calledWorkspaceDirectory.

The easiest way to achieve this is to use the following steps to create a shortcut:

1. Browse to eclipse.exe in Windows Resource Manager and right-click and drag it to create a shortcut for eclipse.exe.
2. Edit shortcuts to makeStartup location:A field identifies the parent directory of a workspace (for example,C:/users/Robert).
3. Close the Properties dialog box and double-click the shortcut (if the provided directory isC:/users/Robert, The workspace location isC:/users/Robert/workspace).

Of course, you can also use a command prompt (by switching the directory to the parent directory of the workspace and then running eclipse.exe) to achieve the same effect.

Use-data to set a specific workspace location

To use-dataCommand Line independent variable, as long-data your_workspace_location(For example,-data c:/users/robert/myworkspace) Added to the shortcut PropertyTargetField or explicitly include it on the command line.

Use-VM to set Java VM

We recommend that you explicitly specify the Java VM to be used when running eclipse. Use-vmCommand Line independent variable (for example,-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 installing other products, they can change your path, resulting in the next time you start eclipse, use another Java VM.

Run advanced topics in eclipse

The eclipse executable file and platform itself provide many execution options for developing or debugging eclipse components of interest. This is a list of common options. For the complete list, see the eclipse runtime Options page in the Platform Plug-in developer guide. The general format for running eclipse executable files is:

eclipse [platform options] [-vmargs [Java VM arguments]]

Eclipse startup parameters

Command	Description	Cause
-arch architecture	Define the processor architecture on which the eclipse Platform runs. The eclipse platform usually uses Javaos.archAttribute Value to calculate the best setting. If this item is specified here, this is the value used by the eclipse platform. The value specified here can be used as bootloader. getosarch () for the plug-in. The example values are: "x86", "iSCSI", "PA-RISC", and "PPC ".	2.0
-application applicationId	The application to run. Applications are declared by providing extensions to the org. Eclipse. Core. runtime. Applications extension points. This independent variable is usually not required. If this option is specified, the value overwrites the value provided by the configuration. If this option is not specified, the "Eclipse workbench" is run ".	1.0
-configuration configurationFileURL	The location of the configuration file on the eclipse platform, which is expressed as a URL. The configuration file determines the location of the eclipse platform, available plug-in sets, and main functional components. Note that relative URLs are not allowed. When the eclipse platform is installed or updated, the configuration file is written to this location.	2.0
-consolelog	Mirror the error logs of the eclipse platform to the console used to run eclipse. And-debugIt is easy to use in combination.	1.0
-data workspacePath	The path of the workspace to run the eclipse platform. The workspace location is also the default location of the project. The relative path is interpreted relative to the directory from which eclipse is started.	1.0
-debug [optionsFile]	Place the platform in the debugging mode and load debugging options (if specified) from the file at the given location ). This file indicates which debugging points can be used for plug-ins and whether they are enabled. If no file location is provided, the platform searches for a file named ". Options" in the directory where eclipse is started. The URL and file system path can be used as the file location.	1.0
-dev [classpathEntries]	Place the platform in the development mode. Add optional class path entries (separated by commas) to the runtime class path of each plug-in. For example, when a workspace contains a plug-in to be developed, specify-dev binThe name of each plug-in project isbinTo store the most recently generated class files. Removes redundant or non-existent class path entries.	1.0
-keyring keyringFilePath	The location of the authorized database (or "key ring" file) on the disk. This independent variable must be-passwordOption. The relative path is interpreted relative to the directory from which eclipse is started.	1.0
-nl locale	Defines the name of the language environment on which the eclipse Platform runs. The eclipse platform usually automatically calculates the best settings. If this item is specified here, this is the value used by the eclipse platform. The value specified here can be used as bootloader. getnl () for the plug-in. The example values include "en_us" and "fr_fr_euro ".	2.0
-nosplash	Run the platform without displaying the startup screen.	1.0
-os operatingSystem	Defines the operating system on which the eclipse Platform runs. The eclipse platform usually uses Javaos.nameAttribute Value to calculate the best setting. If this item is specified here, this is the value used by the eclipse platform. The value specified here can be used as bootloader. getos () for the plug-in and used to parse the path mentioned in the plug-in list file.$os$Variable. Example values: "Win32", "Linux", "HPUX", "Solaris", and "Aix ".	1.0
-password password	The password of the authorized database. And-keyringOption.	1.0
-perspective perspectiveId	The perspective that needs to be opened in the active workbench window at startup. If this parameter is not specified, the perspective of the activity when it is disabled is enabled.	1.0
-plugincustomization propertiesFile	Location of the property file that contains the default setting of the plug-in preferences. These default settings overwrite the default settings specified in the main feature. The relative path is interpreted relative to the directory from which eclipse is started.	2.0
-product productId	The identifier of the product to run. This product provides the product customization information for the startup instances of eclipse and determines its use. This option is replaced by feature, which is still supported due to compatibility reasons.	3.0
-refresh	The global refresh option of the workspace is executed at startup. This will make any changes made in the file system since the last running of the platform consistent.	1.0
-showlocation	Option used to display the workspace location in the title bar of the window. In Release 2.0, this option is only used with the-Data command line argument.	2.0
-vm vmPath	The location of the "Java Runtime Environment" (JRE) used to run the eclipse platform. If this option is not specified, JRE is located injre(It is the sibling directory of the eclipse executable file ). The relative path is interpreted relative to the directory from which eclipse is started.	1.0
-vmargs args	When passed to eclipse, this option is used to customize the Java VM operations used to run eclipse. If this option is specified, it must be at the end of the command line. The given independent variable depends on the VM to run.	1.0

Pass all the independent variables (but not including-vmargs) after the-vmargs entry as the virtual machine independent variables (that is, before the class to be run) directly to the indicated Java VM.Note:If eclipse starts the independent variables (for example,-data) provided after the Java VM independent variable (-vmargs), eclipse will not start and you will receive the "JVM terminated. Exit code 1 error.

Run eclipse on j9 on different VMS

When running eclipse on j9 1.5, we recommend 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 2.0, the default independent variable selected by j9w should be the appropriate option. However, to overwrite the parameters automatically set in the eclipse executable file, you must specify-vmargs without any parameters, as shown below:

eclipse.exe [eclipse arguments] -vm path_to_j9w.exe -vmargs

For more information, see j9 VM documentation and help.

Run eclipse on IBM developer kit, Java (TM) technology edition VM

The default VM settings for IBM developer kit, Java (TM) technology edition 1.3 Linux are suitable for initial research, but are insufficient for large-scale development. For large-scale development, Vm independent variables should be modified to make more heaps available. For example, the following settings allow the Java heap to increase to 256 MB:

-vmargs -Xmx256M