1
<?xml version="1.0" encoding="UTF-8"?>
3
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
4
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
5
<!-- lifted from troff+man by doclifter -->
6
<refentry id='eclipse1'>
8
<refentrytitle>eclipse</refentrytitle>
9
<manvolnum>1</manvolnum>
11
<refnamediv id='name'>
12
<refname>eclipse</refname>
13
<refpurpose>extensible tool platform and Java IDE</refpurpose>
15
<!-- body begins here -->
16
<refsynopsisdiv id='synopsis'>
18
<command>eclipse</command>
19
<arg choice='opt'><arg choice='plain'><replaceable>platform</replaceable></arg><arg choice='plain'><replaceable>options</replaceable></arg></arg>
20
<arg choice='opt'><arg choice='plain'>-vmargs </arg><arg choice='opt'><arg choice='plain'><replaceable>Java</replaceable></arg><arg choice='plain'><replaceable>VM</replaceable></arg><arg choice='plain'><replaceable>arguments</replaceable></arg></arg></arg>
25
<refsect1 id='description'><title>DESCRIPTION</title>
27
The <command>Eclipse</command> Platform is an open and
28
extensible platform for anything and yet nothing in particular. It provides a
29
foundation for constructing and running integrated software-development tools.
30
The <command>Eclipse</command> Platform allows tool builders
31
to independently develop tools that integrate with other people's tools so
32
seamlessly you can't tell where one tool ends and another starts.</para>
34
<para>When invoked without selecting any particular application, the <command>eclipse</command>
35
command will start the <command>Eclipse</command> Platform with the Java Development
36
Tools (JDT) functionality enabled and ready to use.</para>
38
<para>This manual page documents the command-line arguments for the
39
<command>Eclipse</command> Platform and it is based on the
40
Runtime Options help item in the <command>Eclipse</command>
41
<ulink url="#authors" xrefstyle="AUTHORS">online help</ulink><!-- (see xref endterm="authors" linkend="authors" xrefstyle="AUTHORS"></xref> AUTHORS below)-->.</para>
45
<refsect1 id='platform_options'><title>PLATFORM OPTIONS</title>
46
<para> Listed below are the command line arguments processed by various parts of the
47
<command>Eclipse</command> runtime.
48
Many of these values can also be specified using System properties either on the command line
49
using <command>-D VM</command> arguments, by specifying their values in a <filename>config.ini</filename> file or by using a
50
<filename><launcher>.ini</filename> file. Using the two latter techniques it is possible to customize
51
<command>Eclipse</command> without using command line arguments at all.</para>
53
<para>For each argument in the list, its corresponding System property key is given (in {}). Also
54
given is the <command>Eclipse</command> runtime layer in which the
55
command line argument is processed (in ()). </para>
57
<variablelist remap='TP'>
61
-application <id> (Runtime)
65
The identifier of the application to run. The value given here
66
overrides any application defined by the product being run</para>
68
This is equivalent to setting the property
69
<emphasis>eclipse.application</emphasis> to
76
-arch <architecture> (OSGi)
79
<para>The processor architecture value.</para>
81
This is equivalent to setting the property <emphasis>osgi.arch</emphasis> to
92
If set to "true", any cached data used by the OSGi
93
framework and eclipse runtime will be wiped clean. This will clean
94
the caches used to store bundle dependency resolution and eclipse
95
extension registry data. Using this option will force eclipse to
96
reinitialize these caches.
99
This is equivalent to setting the property <emphasis>osgi.clean</emphasis> to
106
-configuration <location> (Main)
109
<para>The configuration location for this run of the platform. The
110
configuration determines what plug-ins will run as well as various
111
other system settings. See the On-line Help for details (SEE ALSO below).</para>
113
This is equivalent to setting the property <emphasis>osgi.configuration.area</emphasis>
120
-console [port] (OSGi)
123
<para>If set to a non-null value, the OSGi console (if installed) is
124
enabled. If the value is a suitable integer, it is interpreted as
125
the port on which the console listens and directs its output to the
126
given port. Handy for investigating the state of the system.</para>
128
This is equivalent to setting the property <emphasis>osgi.console</emphasis> to [port] or the
129
empty string if the default port is to be used (i.e., when the port is not specified).
135
-consoleLog (Runtime)
138
<para>If "true", any log output is also sent to Java's
139
System.out (typically back to the command shell if any). Handy when
140
combined with -debug.</para>
142
This is equivalent to setting the property <emphasis>eclipse.consoleLog</emphasis> to
149
-data <location> (OSGi)<literallayout></literallayout>
153
This is equivalent to setting the property <emphasis>osgi.instance.area</emphasis> to
160
-debug [options file] (OSGi)
164
This is equivalent to setting the property <emphasis>osgi.debug</emphasis> to
165
[options file] or the empty string to simply enable debug (i.e., if
166
the options file location is not specified).
172
-dev [entries] (OSGi)
176
This is equivalent to setting the property <emphasis>osgi.dev</emphasis> to
177
[entries] or the empty string to simply enable dev mode (i.e., if
178
entries are not specified).
184
-eclipse.keyring <file path> (Equinox)
188
Set to override location of the default secure storage.
194
-eclipse.password <file path> (Equinox)
198
If specified, the secure storage treats contents of the file as a
199
default password. When not set, password providers are used to
206
-feature <feature id> (Runtime)
210
This is equivalent to setting the property <emphasis>eclipse.product</emphasis> to <feature
217
-framework <location> (Main)
221
This is equivalent to setting the property <emphasis>osgi.framework</emphasis> to
232
Initializes the configuration being run. All runtime related data
233
structures and caches are refreshed. Any user/plug-in defined
234
configuration data is not purged. No application is run, any
235
product specifications are ignored and no UI is presented (e.g.,
236
the splash screen is not drawn).
242
-install <location> (Main)
246
This is equivalent to setting the property <emphasis>osgi.install.area</emphasis> to
253
-keyring <location> (Runtime)
257
The location of the authorization database on disk. This argument
258
has to be used together with the -password argument.
264
--launcher.library <location> (Executable)
268
The location of the eclipse executable's companion shared
269
library. If not specified the executable looks in the plugins
270
directory for the appropriate
271
org.eclipse.equinox.launcher.[platform] fragment with the highest
272
version and uses the shared library named eclipse_* inside.
278
--launcher.ini <location> (Executable)
282
<!-- NOTE ECLIPSE.EXE HERE -->
283
The location of the product .ini file to use. If not
284
specified the executable will look for a file beside the launcher
285
with the same name and the extension .ini. (ie eclipse.exe
286
looks for eclipse.ini, product.exe looks for product.ini).
292
--launcher.suppressErrors (Executable)
296
If specified the executable will not display any error or message
297
dialogs. This is useful if the executable is being used in an
298
unattended situation.
304
--launcher.XXMaxPermSize <value> (Executable)
308
If specified, and the executable detects that the VM being used is
309
a Sun VM, then the launcher will automatically add the
310
-XX:MaxPermSize=<value> vm argument. The executable is
311
not capable of detecting Sun VMs on all
312
platforms.<literallayout></literallayout>
322
The name to be displayed in task bar item when the application
323
starts up. When not set, the name is the name of the executable.
329
-nl <locale> (OSGi)
333
This is equivalent to setting the property
334
<emphasis>osgi.nl</emphasis> to
345
This is equivalent to setting the property
346
<emphasis>osgi.noShutdown</emphasis> to
353
-noLazyRegistryCacheLoading (Runtime)
357
This is equivalent to setting the property
358
<emphasis>eclipse.noLazyRegistryCacheLoading</emphasis>
365
-noRegistryCache (Runtime)
369
This is equivalent to setting the property
370
<emphasis>eclipse.noRegistryCache</emphasis>
377
-noSplash (Executable, Main)
381
Controls whether or not the splash screen is shown.
387
-os <operating system> (OSGi)
391
This is equivalent to setting the property
392
<emphasis>osgi.os</emphasis> to
393
<operating system>.
399
-password <password> (Runtime)
403
The password for the authorization database.
409
-pluginCustomization <location> (Runtime)
413
This is equivalent to setting the property
414
<emphasis>eclipse.pluginCustomization</emphasis>
421
-product <id> (OSGi)
425
This is equivalent to setting the property
426
<emphasis>eclipse.product</emphasis> to <id>.
432
-showSplash <bitmap> (Executable, Main)
436
Specifies the bitmap to use in the splash screen. If specified, the
437
launcher may be able to show the splash screen before starting the
438
Java VM. If not specified, Main will find the bitmap using
439
the <emphasis>osgi.splashLocation</emphasis> and <emphasis>osgi.splashPath</emphasis>
440
properties.<literallayout></literallayout>
446
-startup <location> (Executable)
450
The location of jar used to startup eclipse. The jar referred to
451
should have the Main-Class attribute set to
452
org.eclipse.equinox.launcher.Main. If this parameter is not set,
453
the executable will look in the plugins directory for
454
theorg.eclipse.equinox.launcher bundle with the highest
455
version.<literallayout></literallayout>
461
-user <location> (OSGi)
465
This is equivalent to setting the property
466
<emphasis>osgi.user.area</emphasis> to
473
-vm <path to java vm> (Executable, Main)
477
<!-- NOTE JVM.DLL HERE -->
478
When passed to the Eclipse executable, this option is used to
479
locate the Java VM to use to run Eclipse. It should be the full
480
file system path to an appropriate: Java jre/bin directory, Java
481
Executable, Java shared library (jvm.dll or libjvm.so), or a Java
482
VM Execution Environment description file. If not specified,
483
the Eclipse executable uses a search algorithm to locate a suitable
484
VM. In any event, the executable then passes the path to the actual
485
VM used to Java Main using the -vm argument. Java Main then stores
486
this value in <emphasis>eclipse.vm</emphasis>.
492
-vmargs [vmargs*] (Executable, Main)
496
when passed to the Eclipse, this option is used to customize the
497
operation of the Java VM to use to run Eclipse. If specified, this
498
option must come at the end of the command line. Even if not
499
specified on the executable command line, the executable will
500
automatically add the relevant arguments (including the class being
501
launched) to the command line passed into Java using the -vmargs
502
argument. Java Main then stores this value in
503
<emphasis>eclipse.vmargs</emphasis>.
509
-ws <window system> (OSGi)
513
This is equivalent to setting the property
514
<emphasis>osgi.ws</emphasis> to
515
<window system>.
523
<refsect1 id='see_also'><title>SEE ALSO</title>
524
<para><citerefentry><refentrytitle>java</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
525
<citerefentry><refentrytitle>ecj</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
526
<para><command>Eclipse</command> On-line Help <ulink url='http://help.eclipse.org/'>http://help.eclipse.org/</ulink>
527
<glossterm>Platform Plug-in Developer Guide</glossterm> > <glossterm>Reference</glossterm> > <glossterm>Other reference information</glossterm> >
528
<glossterm>Runtime Options</glossterm>.</para>
532
<refsect1 id='files'><title>FILES</title>
533
<para>The system wide config.ini file is <filename>/etc/eclipse.ini</filename>. User level Configuration file is
534
<filename>$HOME/.eclipse/org.eclipse.platform_<version>_<id>/configuration/config.ini</filename>.</para>
537
<refsect1 XrefLabel="AUTHORS" id="authors"><title>AUTHORS</title>
539
The <command>Eclipse</command> Project was originally created by IBM in November 2001 and
540
supported by a consortium of software vendors. The <command>Eclipse</command> Foundation was
541
created in January 2004 as an independent not-for-profit corporation to act as the steward of the
542
<command>Eclipse</command> community.
544
<para>This manual page was semi-automatically transformed from the
545
Runtime Options HTML help using <command>pandoc</command> and
546
<command>docbook2x-man</command> by Pablo Duboue <pablo.duboue@gmail.com>.</para>