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 "FAQ How do I run Eclipse?"
m (→See Also:) |
|||
Line 26: | Line 26: | ||
eclipse -vm c:/jre/bin/javaw.exe | eclipse -vm c:/jre/bin/javaw.exe | ||
</pre> | </pre> | ||
− | Another option is to put startup configuration into an | + | Another option is to put startup configuration into an <code>[[eclipse.ini]]</code> file. The Eclipse program launcher will read arguments from either the command-line or the configuration file named <code>[[eclipse.ini]]</code>. To specify a JVM using configuration file, create a text file named <code>[[eclipse.ini]]</code> in the same folder as <code>eclipse.exe</code> with these contents: |
<pre> | <pre> | ||
-vm | -vm | ||
c:/jre/bin/javaw.exe | c:/jre/bin/javaw.exe | ||
</pre> | </pre> | ||
− | Eclipse now will launch without additional arguments in the command-line, with the JVM specified in the | + | Eclipse now will launch without additional arguments in the command-line, with the JVM specified in the <code>[[eclipse.ini]]</code> configuration file. Windows users: please be sure that the file you created has .ini extension, you may need to uncheck the 'Folder Options:View:Hide file extensions for known file types' from the Windows Explorer's Tools menu.. |
You should always use <tt>-vm</tt> so you can be sure of what VM you are using. | You should always use <tt>-vm</tt> so you can be sure of what VM you are using. | ||
Line 49: | Line 49: | ||
workspaces for versions before Eclipse 3.0 is to create shortcuts or shell | workspaces for versions before Eclipse 3.0 is to create shortcuts or shell | ||
scripts for each launch. | scripts for each launch. | ||
+ | |||
The use of <tt>-data</tt> is advised because using the default workspace location | The use of <tt>-data</tt> is advised because using the default workspace location | ||
will make it much more difficult for you to upgrade to new versions of Eclipse. | will make it much more difficult for you to upgrade to new versions of Eclipse. |
Revision as of 12:12, 28 February 2007
When you unzip the Eclipse SDK, it creates a base install directory called eclipse. The directory layout looks something like this:
eclipse/ features/ ''the directory containing Eclipse features'' plugins/ ''the directory containing Eclipse plugins'' eclipse.exe ''platform executable'' cpl-v10.html ''the CPL license'' install.ini jre/ ''the JRE to run Eclipse with'' notice.html readme startup.jar ''classes needed to start the platform''
You can start Eclipse by running eclipse.exe on Windows or eclipse on other platforms. This small launcher runs a JVM with the following arguments:
java -cp eclipse/startup.jar org.eclipse.core.launcher.Main
If available under the eclipse/jre directory, the Eclipse JRE will be used; otherwise the launcher will consult the JAVA_HOME system path variable. To explicitly specify a JVM of your choice, you can use the -vm command line argument:
eclipse -vm c:/jre/bin/javaw.exe
Another option is to put startup configuration into an eclipse.ini
file. The Eclipse program launcher will read arguments from either the command-line or the configuration file named eclipse.ini
. To specify a JVM using configuration file, create a text file named eclipse.ini
in the same folder as eclipse.exe
with these contents:
-vm c:/jre/bin/javaw.exe
Eclipse now will launch without additional arguments in the command-line, with the JVM specified in the eclipse.ini
configuration file. Windows users: please be sure that the file you created has .ini extension, you may need to uncheck the 'Folder Options:View:Hide file extensions for known file types' from the Windows Explorer's Tools menu..
You should always use -vm so you can be sure of what VM you are using. Installers for other applications sometimes modify the JAVA_HOME variable, thus changing the VM used to launch Eclipse without your knowing about it.
The first time the eclipse command is executed, the platform creates a workspace directory, such as eclipse/workspace. The workspace will contain all your projects, along with private metadata computed by various plug-ins.
In Eclipse 3.0, you are prompted to choose a workspace location on start-up. Previously, the platform stored the workspace in the Eclipse install directory by default. In all versions of Eclipse, you can manually specify the workspace location on the command line, using the -data <workspace-path> command-line argument. The easiest way to quickly start Eclipse on different workspaces for versions before Eclipse 3.0 is to create shortcuts or shell scripts for each launch.
The use of -data is advised because using the default workspace location will make it much more difficult for you to upgrade to new versions of Eclipse.
See Also:
- FAQ How do I increase the heap size available to Eclipse?
- FAQ How do I increase the permgen size available to Eclipse?
- FAQ Who shows the Eclipse splash screen?
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.