[SCM] eclipse - Powerful IDE written in java - Debian package. branch, master, updated. 54742912614d8fe6472baf02485e7c3cb1cf39ae
Benjamin Drung
bdrung-guest at alioth.debian.org
Mon Feb 1 08:09:44 UTC 2010
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "eclipse - Powerful IDE written in java - Debian package.".
The branch, master has been updated
via 54742912614d8fe6472baf02485e7c3cb1cf39ae (commit)
from ece6b71b562894a97630a93f04cba9fe25979657 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 54742912614d8fe6472baf02485e7c3cb1cf39ae
Author: Benjamin Drung <bdrung at ubuntu.com>
Date: Mon Feb 1 09:09:18 2010 +0100
Update eclipse manpage to final version.
-----------------------------------------------------------------------
Summary of changes:
debian/patches/eclipse-manpage.patch | 178 +++++++++++++++++++++++-----------
eclipse.1.xml | 137 +++++++++++++++++++-------
2 files changed, 222 insertions(+), 93 deletions(-)
diff --git a/debian/patches/eclipse-manpage.patch b/debian/patches/eclipse-manpage.patch
index 23e14e5..9fff2ea 100644
--- a/debian/patches/eclipse-manpage.patch
+++ b/debian/patches/eclipse-manpage.patch
@@ -1,33 +1,12 @@
Description: Add eclipse manpage
-Author: Benjamin Drung <bdrung at ubuntu.com>
+Author: Pablo Duboue <pablo.duboue at gmail.com>
Bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=30107
Bug-Ubuntu: https://launchpad.net/bugs/494065
-diff --git a/build.xml b/build.xml
-index 19ba175..bb41674 100644
---- a/build.xml
-+++ b/build.xml
-@@ -791,6 +791,12 @@
- <!-- eclipse binary -->
- <mkdir dir="${destDir}${prefix}/bin" />
- <symlink link="${destDir}${prefix}/bin/eclipse" resource="../${libDir}/eclipse/eclipse" />
-+ <!-- eclipse manpage -->
-+ <mkdir dir="${destDir}${prefix}/share/man/man1" />
-+ <exec executable="docbook2x-man" failonerror="true">
-+ <arg value="eclipse.1.xml" />
-+ </exec>
-+ <move file="eclipse.1" tofile="${destDir}${prefix}/share/man/man1/eclipse.1" />
- <!-- Create the "startup.jar" symlink -->
- <fileset dir="${destDir}/${prefix}/${libDir}/eclipse/plugins" includes="org.eclipse.equinox.launcher_*" id="startupjar" />
- <property name="startupjarpath" refid="startupjar" />
-diff --git a/eclipse.1.xml b/eclipse.1.xml
-new file mode 100644
-index 0000000..e49139a
--- /dev/null
-+++ b/eclipse.1.xml
-@@ -0,0 +1,549 @@
++++ eclipse-3.5.1+repack/eclipse.1.xml
+@@ -0,0 +1,616 @@
+<?xml version="1.0" encoding="UTF-8"?>
-+
+ <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
+ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
+<!-- lifted from troff+man by doclifter -->
@@ -91,7 +70,7 @@ index 0000000..e49139a
+ <listitem>
+ <para>
+ The identifier of the application to run. The value given here
-+ overrides any application defined by the product being run</para>
++ overrides any application defined by the product being run.</para>
+ <para>
+ This is equivalent to setting the property
+ <emphasis>eclipse.application</emphasis> to
@@ -117,10 +96,10 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
-+ If set to "true", any cached data used by the OSGi
-+ framework and eclipse runtime will be wiped clean. This will clean
-+ the caches used to store bundle dependency resolution and eclipse
-+ extension registry data. Using this option will force eclipse to
++ Wipe clean any cached data used by the OSGi
++ framework and <command>eclipse</command> runtime. This will clean
++ the caches used to store bundle dependency resolution and <command>eclipse</command>
++ extension registry data. Using this option will force <command>eclipse</command> to
+ reinitialize these caches.
+ </para>
+ <para>
@@ -148,8 +127,7 @@ index 0000000..e49139a
+ -console [port] (OSGi)
+ </option></term>
+ <listitem>
-+ <para>If set to a non-null value, the OSGi console (if installed) is
-+ enabled. If the value is a suitable integer, it is interpreted as
++ <para>Enable the OSGi console (if installed). If the [port] value is a suitable integer, it is interpreted as
+ the port on which the console listens and directs its output to the
+ given port. Handy for investigating the state of the system.</para>
+ <para>
@@ -163,9 +141,9 @@ index 0000000..e49139a
+ -consoleLog (Runtime)
+ </option></term>
+ <listitem>
-+ <para>If "true", any log output is also sent to Java's
++ <para>Any log output is also sent to Java's
+ System.out (typically back to the command shell if any). Handy when
-+ combined with -debug.</para>
++ combined with <command>-debug</command>.</para>
+ <para>
+ This is equivalent to setting the property <emphasis>eclipse.consoleLog</emphasis> to
+ "true".
@@ -177,6 +155,11 @@ index 0000000..e49139a
+ -data <location> (OSGi)<literallayout></literallayout>
+ </option></term>
+ <listitem>
++ <para>The instance data location for this session. Plug-ins use this
++ location to store their data. For example, the Resources plug-in
++ uses this as the default location for projects (aka the workspace).
++ See the On-line Help for details (SEE ALSO below).
++ </para>
+ <para>
+ This is equivalent to setting the property <emphasis>osgi.instance.area</emphasis> to
+ <location>.
@@ -188,6 +171,11 @@ index 0000000..e49139a
+ -debug [options file] (OSGi)
+ </option></term>
+ <listitem>
++ <para>Put the platform in debug mode. If [options file] is given, it is interpreted as the location of the
++ <filename>.options</filename> file. This file indicates what debug points are available
++ for a plug-in and whether or not they are enabled. If a location is
++ not specified, the platform searches for the<filename> .options</filename> file under
++ the install directory.</para>
+ <para>
+ This is equivalent to setting the property <emphasis>osgi.debug</emphasis> to
+ [options file] or the empty string to simply enable debug (i.e., if
@@ -200,6 +188,12 @@ index 0000000..e49139a
+ -dev [entries] (OSGi)
+ </option></term>
+ <listitem>
++ <para>Turn on dev mode. If given, [entries] should be a comma-separated class path entries
++ which are added to the class path of each plug-in or a URL to a
++ Java properties file containing custom classpath additions for a
++ set of plug-ins. For each plug-in requiring a customized dev time
++ classpath the file will contain an entry of the
++ form.</para>
+ <para>
+ This is equivalent to setting the property <emphasis>osgi.dev</emphasis> to
+ [entries] or the empty string to simply enable dev mode (i.e., if
@@ -235,6 +229,10 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
++ Set the identifier of the product being run. This controls various
++ branding information and what application is used.
++ </para>
++ <para>
+ This is equivalent to setting the property <emphasis>eclipse.product</emphasis> to <feature
+ id>.
+ </para>
@@ -245,6 +243,9 @@ index 0000000..e49139a
+ -framework <location> (Main)
+ </option></term>
+ <listitem>
++ <para>
++ Set the URL location of the OSGi framework. Useful if the <command>Eclipse</command>
++ install is disjoint. See the On-line Help for details (SEE ALSO below).</para>
+ <para>
+ This is equivalent to setting the property <emphasis>osgi.framework</emphasis> to
+ <location>.
@@ -270,6 +271,9 @@ index 0000000..e49139a
+ -install <location> (Main)
+ </option></term>
+ <listitem>
++ <para>Set the install location of the platform. This option indicates the
++ location of the basic <command>Eclipse</command> plug-ins and is useful if the <command>Eclipse</command>
++ install is disjoint.</para>
+ <para>
+ This is equivalent to setting the property <emphasis>osgi.install.area</emphasis> to
+ <location>.
@@ -283,7 +287,7 @@ index 0000000..e49139a
+ <listitem>
+ <para>
+ The location of the authorization database on disk. This argument
-+ has to be used together with the -password argument.
++ has to be used together with the <command>-password</command> argument.
+ </para>
+ </listitem>
+ </varlistentry>
@@ -293,11 +297,11 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
-+ The location of the eclipse executable's companion shared
++ The location of the <command>eclipse</command> 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.
++ <emphasis>org.eclipse.equinox.launcher.[platform] fragment</emphasis> with the highest
++ version and uses the shared library named <filename>eclipse_*</filename> inside.
+ </para>
+ </listitem>
+ </varlistentry>
@@ -307,11 +311,11 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
-+ <!-- NOTE ECLIPSE.EXE HERE -->
+ The location of the product .ini file to use. If not
+ specified the executable will look for a file beside the launcher
-+ with the same name and the extension .ini. (ie eclipse.exe
-+ looks for eclipse.ini, product.exe looks for product.ini).
++ with the same name and the extension <filename>.ini</filename>. (ie., <filename>/usr/bin/eclipse</filename>
++ looks for <filename>eclipse.ini</filename>, <filename>/opt/product</filename> looks for
++ <filename>product.ini</filename>).
+ </para>
+ </listitem>
+ </varlistentry>
@@ -337,7 +341,7 @@ index 0000000..e49139a
+ a Sun VM, then the launcher will automatically add the
+ -XX:MaxPermSize=<value> vm argument. The executable is
+ not capable of detecting Sun VMs on all
-+ platforms.<literallayout></literallayout>
++ platforms.
+ </para>
+ </listitem>
+ </varlistentry>
@@ -358,6 +362,10 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
++ The name of the locale on which <command>Eclipse</command> platform will run. NL
++ values should follow the standard Java locale naming conventions.
++ </para>
++ <para>
+ This is equivalent to setting the property
+ <emphasis>osgi.nl</emphasis> to
+ <locale>.
@@ -370,6 +378,11 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
++ Disable automatic termination of the VM after the <command>eclipse</command>
++ application has ended. This is useful for examining the OSGi
++ framework after the <command>eclipse</command> application has ended.
++ </para>
++ <para>
+ This is equivalent to setting the property
+ <emphasis>osgi.noShutdown</emphasis> to
+ "true".
@@ -382,6 +395,13 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
++ Deactivate the platform's plug-in registry cache loading
++ optimization. By default, configuration elements are
++ loaded from the registry cache (when available) only on demand,
++ reducing memory footprint. This option forces the registry cache to
++ be fully loaded at startup.
++ </para>
++ <para>
+ This is equivalent to setting the property
+ <emphasis>eclipse.noLazyRegistryCacheLoading</emphasis>
+ to "true".
@@ -394,6 +414,10 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
++ The internal extension registry cache will
++ neither be read nor written.
++ </para>
++ <para>
+ This is equivalent to setting the property
+ <emphasis>eclipse.noRegistryCache</emphasis>
+ to "true".
@@ -416,6 +440,10 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
++ The operating system value. The value should be one of the <command>Eclipse</command>
++ processor architecture names known to <command>Eclipse</command> (e.g., x86, sparc,
++ ...).
++ </para> <para>
+ This is equivalent to setting the property
+ <emphasis>osgi.os</emphasis> to
+ <operating system>.
@@ -438,6 +466,13 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
++ The file system 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 current working directory for
++ <command>eclipse</command> itself.
++ </para>
++ <para>
+ This is equivalent to setting the property
+ <emphasis>eclipse.pluginCustomization</emphasis>
+ to <location>
@@ -450,6 +485,10 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
++ The identifier of the product being run. This controls various
++ branding information and what application is used.
++ </para>
++ <para>
+ This is equivalent to setting the property
+ <emphasis>eclipse.product</emphasis> to <id>.
+ </para>
@@ -463,9 +502,9 @@ index 0000000..e49139a
+ <para>
+ Specifies the bitmap to use in the splash screen. If specified, the
+ launcher may be able to show the splash screen before starting the
-+ Java VM. If not specified, Main will find the bitmap using
++ Java VM. If not specified, Main will find the bitmap using
+ the <emphasis>osgi.splashLocation</emphasis> and <emphasis>osgi.splashPath</emphasis>
-+ properties.<literallayout></literallayout>
++ properties.
+ </para>
+ </listitem>
+ </varlistentry>
@@ -475,12 +514,12 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
-+ The location of jar used to startup eclipse. The jar referred to
-+ should have the Main-Class attribute set to
-+ org.eclipse.equinox.launcher.Main. If this parameter is not set,
++ The location of jar used to startup <command>eclipse</command>. The jar referred to
++ should have the <emphasis>Main-Class</emphasis> attribute set to
++ <emphasis>org.eclipse.equinox.launcher.Main</emphasis>. If this parameter is not set,
+ the executable will look in the plugins directory for
-+ theorg.eclipse.equinox.launcher bundle with the highest
-+ version.<literallayout></literallayout>
++ the <emphasis>org.eclipse.equinox.launcher bundle</emphasis> with the highest
++ version.
+ </para>
+ </listitem>
+ </varlistentry>
@@ -490,6 +529,11 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
++ Set the location of the user area. The user area contains data (e.g.,
++ preferences) specific to the OS user and independent of any <command>Eclipse</command>
++ install, configuration or instance. See the On-line Help for details (SEE ALSO below).
++ </para>
++ <para>
+ This is equivalent to setting the property
+ <emphasis>osgi.user.area</emphasis> to
+ <location>.
@@ -502,15 +546,14 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
-+ <!-- NOTE JVM.DLL HERE -->
-+ When passed to the Eclipse executable, this option is used to
-+ locate the Java VM to use to run Eclipse. It should be the full
-+ file system path to an appropriate: Java jre/bin directory, Java
-+ Executable, Java shared library (jvm.dll or libjvm.so), or a Java
++ When passed to the <command>Eclipse</command> executable, this option is used to
++ locate the Java VM to use to run <command>Eclipse</command>. It should be the full
++ file system path to an appropriate: Java<filename> jre/bin</filename> directory, Java
++ Executable, Java shared library (<filename>libjvm.so</filename>), or a Java
+ VM Execution Environment description file. If not specified,
-+ the Eclipse executable uses a search algorithm to locate a suitable
++ the <command>Eclipse</command> executable uses a search algorithm to locate a suitable
+ VM. In any event, the executable then passes the path to the actual
-+ VM used to Java Main using the -vm argument. Java Main then stores
++ VM used to Java Main using the <command>-vm</command> argument. Java Main then stores
+ this value in <emphasis>eclipse.vm</emphasis>.
+ </para>
+ </listitem>
@@ -521,12 +564,12 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
-+ when passed to the Eclipse, this option is used to customize the
-+ operation of the Java VM to use to run Eclipse. If specified, this
++ when passed to the <command>Eclipse</command>, this option is used to customize the
++ operation of the Java VM to use to run <command>Eclipse</command>. If specified, this
+ option must come at the end of the command line. Even if not
+ specified on the executable command line, the executable will
+ automatically add the relevant arguments (including the class being
-+ launched) to the command line passed into Java using the -vmargs
++ launched) to the command line passed into Java using the <command>-vmargs</command>
+ argument. Java Main then stores this value in
+ <emphasis>eclipse.vmargs</emphasis>.
+ </para>
@@ -538,6 +581,10 @@ index 0000000..e49139a
+ </option></term>
+ <listitem>
+ <para>
++ Set the window system value. The value should be one of the <command>Eclipse</command>
++ window system names known to <command>Eclipse</command> (e.g., win32, motif, ...).
++ </para>
++ <para>
+ This is equivalent to setting the property
+ <emphasis>osgi.ws</emphasis> to
+ <window system>.
@@ -575,3 +622,18 @@ index 0000000..e49139a
+
+</refsect1>
+</refentry>
+--- eclipse-3.5.1+repack.orig/build.xml
++++ eclipse-3.5.1+repack/build.xml
+@@ -791,6 +791,12 @@
+ <!-- eclipse binary -->
+ <mkdir dir="${destDir}${prefix}/bin" />
+ <symlink link="${destDir}${prefix}/bin/eclipse" resource="../${libDir}/eclipse/eclipse" />
++ <!-- eclipse manpage -->
++ <mkdir dir="${destDir}${prefix}/share/man/man1" />
++ <exec executable="docbook2x-man" failonerror="true">
++ <arg value="eclipse.1.xml" />
++ </exec>
++ <move file="eclipse.1" tofile="${destDir}${prefix}/share/man/man1/eclipse.1" />
+ <!-- Create the "startup.jar" symlink -->
+ <fileset dir="${destDir}/${prefix}/${libDir}/eclipse/plugins" includes="org.eclipse.equinox.launcher_*" id="startupjar" />
+ <property name="startupjarpath" refid="startupjar" />
diff --git a/eclipse.1.xml b/eclipse.1.xml
index e49139a..5e883bd 100644
--- a/eclipse.1.xml
+++ b/eclipse.1.xml
@@ -1,5 +1,4 @@
<?xml version="1.0" encoding="UTF-8"?>
-
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
<!-- lifted from troff+man by doclifter -->
@@ -63,7 +62,7 @@ command line argument is processed (in ()). </para>
<listitem>
<para>
The identifier of the application to run. The value given here
- overrides any application defined by the product being run</para>
+ overrides any application defined by the product being run.</para>
<para>
This is equivalent to setting the property
<emphasis>eclipse.application</emphasis> to
@@ -89,10 +88,10 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
- If set to "true", any cached data used by the OSGi
- framework and eclipse runtime will be wiped clean. This will clean
- the caches used to store bundle dependency resolution and eclipse
- extension registry data. Using this option will force eclipse to
+ Wipe clean any cached data used by the OSGi
+ framework and <command>eclipse</command> runtime. This will clean
+ the caches used to store bundle dependency resolution and <command>eclipse</command>
+ extension registry data. Using this option will force <command>eclipse</command> to
reinitialize these caches.
</para>
<para>
@@ -120,8 +119,7 @@ command line argument is processed (in ()). </para>
-console [port] (OSGi)
</option></term>
<listitem>
- <para>If set to a non-null value, the OSGi console (if installed) is
- enabled. If the value is a suitable integer, it is interpreted as
+ <para>Enable the OSGi console (if installed). If the [port] value is a suitable integer, it is interpreted as
the port on which the console listens and directs its output to the
given port. Handy for investigating the state of the system.</para>
<para>
@@ -135,9 +133,9 @@ command line argument is processed (in ()). </para>
-consoleLog (Runtime)
</option></term>
<listitem>
- <para>If "true", any log output is also sent to Java's
+ <para>Any log output is also sent to Java's
System.out (typically back to the command shell if any). Handy when
- combined with -debug.</para>
+ combined with <command>-debug</command>.</para>
<para>
This is equivalent to setting the property <emphasis>eclipse.consoleLog</emphasis> to
"true".
@@ -149,6 +147,11 @@ command line argument is processed (in ()). </para>
-data <location> (OSGi)<literallayout></literallayout>
</option></term>
<listitem>
+ <para>The instance data location for this session. Plug-ins use this
+ location to store their data. For example, the Resources plug-in
+ uses this as the default location for projects (aka the workspace).
+ See the On-line Help for details (SEE ALSO below).
+ </para>
<para>
This is equivalent to setting the property <emphasis>osgi.instance.area</emphasis> to
<location>.
@@ -160,6 +163,11 @@ command line argument is processed (in ()). </para>
-debug [options file] (OSGi)
</option></term>
<listitem>
+ <para>Put the platform in debug mode. If [options file] is given, it is interpreted as the location of the
+ <filename>.options</filename> file. This file indicates what debug points are available
+ for a plug-in and whether or not they are enabled. If a location is
+ not specified, the platform searches for the<filename> .options</filename> file under
+ the install directory.</para>
<para>
This is equivalent to setting the property <emphasis>osgi.debug</emphasis> to
[options file] or the empty string to simply enable debug (i.e., if
@@ -172,6 +180,12 @@ command line argument is processed (in ()). </para>
-dev [entries] (OSGi)
</option></term>
<listitem>
+ <para>Turn on dev mode. If given, [entries] should be a comma-separated class path entries
+ which are added to the class path of each plug-in or a URL to a
+ Java properties file containing custom classpath additions for a
+ set of plug-ins. For each plug-in requiring a customized dev time
+ classpath the file will contain an entry of the
+ form.</para>
<para>
This is equivalent to setting the property <emphasis>osgi.dev</emphasis> to
[entries] or the empty string to simply enable dev mode (i.e., if
@@ -207,6 +221,10 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
+ Set the identifier of the product being run. This controls various
+ branding information and what application is used.
+ </para>
+ <para>
This is equivalent to setting the property <emphasis>eclipse.product</emphasis> to <feature
id>.
</para>
@@ -217,6 +235,9 @@ command line argument is processed (in ()). </para>
-framework <location> (Main)
</option></term>
<listitem>
+ <para>
+ Set the URL location of the OSGi framework. Useful if the <command>Eclipse</command>
+ install is disjoint. See the On-line Help for details (SEE ALSO below).</para>
<para>
This is equivalent to setting the property <emphasis>osgi.framework</emphasis> to
<location>.
@@ -242,6 +263,9 @@ command line argument is processed (in ()). </para>
-install <location> (Main)
</option></term>
<listitem>
+ <para>Set the install location of the platform. This option indicates the
+ location of the basic <command>Eclipse</command> plug-ins and is useful if the <command>Eclipse</command>
+ install is disjoint.</para>
<para>
This is equivalent to setting the property <emphasis>osgi.install.area</emphasis> to
<location>.
@@ -255,7 +279,7 @@ command line argument is processed (in ()). </para>
<listitem>
<para>
The location of the authorization database on disk. This argument
- has to be used together with the -password argument.
+ has to be used together with the <command>-password</command> argument.
</para>
</listitem>
</varlistentry>
@@ -265,11 +289,11 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
- The location of the eclipse executable's companion shared
+ The location of the <command>eclipse</command> 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.
+ <emphasis>org.eclipse.equinox.launcher.[platform] fragment</emphasis> with the highest
+ version and uses the shared library named <filename>eclipse_*</filename> inside.
</para>
</listitem>
</varlistentry>
@@ -279,11 +303,11 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
- <!-- NOTE ECLIPSE.EXE HERE -->
The location of the product .ini file to use. If not
specified the executable will look for a file beside the launcher
- with the same name and the extension .ini. (ie eclipse.exe
- looks for eclipse.ini, product.exe looks for product.ini).
+ with the same name and the extension <filename>.ini</filename>. (ie., <filename>/usr/bin/eclipse</filename>
+ looks for <filename>eclipse.ini</filename>, <filename>/opt/product</filename> looks for
+ <filename>product.ini</filename>).
</para>
</listitem>
</varlistentry>
@@ -309,7 +333,7 @@ command line argument is processed (in ()). </para>
a Sun VM, then the launcher will automatically add the
-XX:MaxPermSize=<value> vm argument. The executable is
not capable of detecting Sun VMs on all
- platforms.<literallayout></literallayout>
+ platforms.
</para>
</listitem>
</varlistentry>
@@ -330,6 +354,10 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
+ The name of the locale on which <command>Eclipse</command> platform will run. NL
+ values should follow the standard Java locale naming conventions.
+ </para>
+ <para>
This is equivalent to setting the property
<emphasis>osgi.nl</emphasis> to
<locale>.
@@ -342,6 +370,11 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
+ Disable automatic termination of the VM after the <command>eclipse</command>
+ application has ended. This is useful for examining the OSGi
+ framework after the <command>eclipse</command> application has ended.
+ </para>
+ <para>
This is equivalent to setting the property
<emphasis>osgi.noShutdown</emphasis> to
"true".
@@ -354,6 +387,13 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
+ Deactivate the platform's plug-in registry cache loading
+ optimization. By default, configuration elements are
+ loaded from the registry cache (when available) only on demand,
+ reducing memory footprint. This option forces the registry cache to
+ be fully loaded at startup.
+ </para>
+ <para>
This is equivalent to setting the property
<emphasis>eclipse.noLazyRegistryCacheLoading</emphasis>
to "true".
@@ -366,6 +406,10 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
+ The internal extension registry cache will
+ neither be read nor written.
+ </para>
+ <para>
This is equivalent to setting the property
<emphasis>eclipse.noRegistryCache</emphasis>
to "true".
@@ -388,6 +432,10 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
+ The operating system value. The value should be one of the <command>Eclipse</command>
+ processor architecture names known to <command>Eclipse</command> (e.g., x86, sparc,
+ ...).
+ </para> <para>
This is equivalent to setting the property
<emphasis>osgi.os</emphasis> to
<operating system>.
@@ -410,6 +458,13 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
+ The file system 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 current working directory for
+ <command>eclipse</command> itself.
+ </para>
+ <para>
This is equivalent to setting the property
<emphasis>eclipse.pluginCustomization</emphasis>
to <location>
@@ -422,6 +477,10 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
+ The identifier of the product being run. This controls various
+ branding information and what application is used.
+ </para>
+ <para>
This is equivalent to setting the property
<emphasis>eclipse.product</emphasis> to <id>.
</para>
@@ -435,9 +494,9 @@ command line argument is processed (in ()). </para>
<para>
Specifies the bitmap to use in the splash screen. If specified, the
launcher may be able to show the splash screen before starting the
- Java VM. If not specified, Main will find the bitmap using
+ Java VM. If not specified, Main will find the bitmap using
the <emphasis>osgi.splashLocation</emphasis> and <emphasis>osgi.splashPath</emphasis>
- properties.<literallayout></literallayout>
+ properties.
</para>
</listitem>
</varlistentry>
@@ -447,12 +506,12 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
- The location of jar used to startup eclipse. The jar referred to
- should have the Main-Class attribute set to
- org.eclipse.equinox.launcher.Main. If this parameter is not set,
+ The location of jar used to startup <command>eclipse</command>. The jar referred to
+ should have the <emphasis>Main-Class</emphasis> attribute set to
+ <emphasis>org.eclipse.equinox.launcher.Main</emphasis>. If this parameter is not set,
the executable will look in the plugins directory for
- theorg.eclipse.equinox.launcher bundle with the highest
- version.<literallayout></literallayout>
+ the <emphasis>org.eclipse.equinox.launcher bundle</emphasis> with the highest
+ version.
</para>
</listitem>
</varlistentry>
@@ -462,6 +521,11 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
+ Set the location of the user area. The user area contains data (e.g.,
+ preferences) specific to the OS user and independent of any <command>Eclipse</command>
+ install, configuration or instance. See the On-line Help for details (SEE ALSO below).
+ </para>
+ <para>
This is equivalent to setting the property
<emphasis>osgi.user.area</emphasis> to
<location>.
@@ -474,15 +538,14 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
- <!-- NOTE JVM.DLL HERE -->
- When passed to the Eclipse executable, this option is used to
- locate the Java VM to use to run Eclipse. It should be the full
- file system path to an appropriate: Java jre/bin directory, Java
- Executable, Java shared library (jvm.dll or libjvm.so), or a Java
+ When passed to the <command>Eclipse</command> executable, this option is used to
+ locate the Java VM to use to run <command>Eclipse</command>. It should be the full
+ file system path to an appropriate: Java<filename> jre/bin</filename> directory, Java
+ Executable, Java shared library (<filename>libjvm.so</filename>), or a Java
VM Execution Environment description file. If not specified,
- the Eclipse executable uses a search algorithm to locate a suitable
+ the <command>Eclipse</command> executable uses a search algorithm to locate a suitable
VM. In any event, the executable then passes the path to the actual
- VM used to Java Main using the -vm argument. Java Main then stores
+ VM used to Java Main using the <command>-vm</command> argument. Java Main then stores
this value in <emphasis>eclipse.vm</emphasis>.
</para>
</listitem>
@@ -493,12 +556,12 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
- when passed to the Eclipse, this option is used to customize the
- operation of the Java VM to use to run Eclipse. If specified, this
+ when passed to the <command>Eclipse</command>, this option is used to customize the
+ operation of the Java VM to use to run <command>Eclipse</command>. If specified, this
option must come at the end of the command line. Even if not
specified on the executable command line, the executable will
automatically add the relevant arguments (including the class being
- launched) to the command line passed into Java using the -vmargs
+ launched) to the command line passed into Java using the <command>-vmargs</command>
argument. Java Main then stores this value in
<emphasis>eclipse.vmargs</emphasis>.
</para>
@@ -510,6 +573,10 @@ command line argument is processed (in ()). </para>
</option></term>
<listitem>
<para>
+ Set the window system value. The value should be one of the <command>Eclipse</command>
+ window system names known to <command>Eclipse</command> (e.g., win32, motif, ...).
+ </para>
+ <para>
This is equivalent to setting the property
<emphasis>osgi.ws</emphasis> to
<window system>.
hooks/post-receive
--
eclipse - Powerful IDE written in java - Debian package.
More information about the pkg-java-commits
mailing list