[SCM] eclipse - Powerful IDE written in java - Debian package. branch, master, updated. 5f0f6691e876db443869a815f20625db450fb258
Benjamin Drung
bdrung-guest at alioth.debian.org
Sat Jan 30 14:40:19 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 5f0f6691e876db443869a815f20625db450fb258 (commit)
via c9b1442495d0226ce1c79446919113bc25562795 (commit)
via a482c9f18d33e1ff1f3b9de8a1a78454cecd68fb (commit)
via eeb707791b467478c7ffa62e085d4f4abfbc1446 (commit)
via 3cb3a466c1a9a74a448ff97de8397a4f1b8de2e8 (commit)
from c2a5d7d6070fb07db39e627a7fdccbed31b7dd18 (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 5f0f6691e876db443869a815f20625db450fb258
Author: Benjamin Drung <bdrung at ubuntu.com>
Date: Sat Jan 30 15:39:58 2010 +0100
Update debian/changelog.
commit c9b1442495d0226ce1c79446919113bc25562795
Author: Benjamin Drung <bdrung at ubuntu.com>
Date: Sat Jan 30 15:36:05 2010 +0100
Bump Standards-Version to 3.8.4.
commit a482c9f18d33e1ff1f3b9de8a1a78454cecd68fb
Author: Benjamin Drung <bdrung at ubuntu.com>
Date: Sat Jan 30 15:34:41 2010 +0100
Drop replaced libswt-eclipse-java.
commit eeb707791b467478c7ffa62e085d4f4abfbc1446
Author: Benjamin Drung <bdrung at ubuntu.com>
Date: Sat Jan 30 15:33:16 2010 +0100
Add manpage from Pablo Duboue <pablo.duboue at gmail.com>
commit 3cb3a466c1a9a74a448ff97de8397a4f1b8de2e8
Author: Benjamin Drung <bdrung at ubuntu.com>
Date: Sat Jan 30 14:14:33 2010 +0100
Remove debian/bugs, they are all fixed.
-----------------------------------------------------------------------
Summary of changes:
build.xml | 6 +
debian/bugs | 25 --
debian/changelog | 28 +-
debian/control | 5 +-
debian/eclipse-platform.install | 1 +
debian/eclipse-platform.manpages | 1 -
debian/extra/eclipse.1 | 226 -------------
debian/patches/eclipse-manpage.patch | 577 ++++++++++++++++++++++++++++++++++
debian/patches/series | 1 +
eclipse.1.xml | 549 ++++++++++++++++++++++++++++++++
10 files changed, 1147 insertions(+), 272 deletions(-)
diff --git a/build.xml b/build.xml
index 19ba175..00330f9 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/debian/bugs b/debian/bugs
deleted file mode 100644
index 7e506fc..0000000
--- a/debian/bugs
+++ /dev/null
@@ -1,25 +0,0 @@
-Doables/Intend To Fix:
-
-LP: 81900 - Should be doable (but there might be a reason for not doing it). - "Could not create /usr/local/lib/eclipse/.eclipseextension" on startup
-
-Fixed on long term:
-
-541638, LP: 417317, LP: 401402 - Fixed by not having two source packages providing libswt - ${APP} cannot be installed with eclipse/eclipse has broken depends.
-
-Invalids (assuming other is fixed):
-
-LP: 160282 - Invalid if openjdk-6 can be used. - eclipse should require java-gcj-compat.
-LP: 45347 - Invalid if 353360 is fixed. - Use java-common instead of java_home config.
-LP: 208267 - Invalid if 353360 is fixed. - openjdk-6 should be added to java_home.
-
-Check/Verifiy in 3.5:
-
-LP: 313548 - Haven't experienced this in 3.3 nor in 3.4 - "Auto-fix" features broken.
-LP: 419199 - Haven't experienced this in 3.2.2-6.1 nor 3.4.1 - Install problem.
-LP: 400962 - Xulrunner-1.9.1 shouldn't break eclipse 3.5 - VM crash during eclipse start on 64bit Ubuntu.
-353360, LP:36534 - Should be fixed if possible. - Respect alternatives.
-358594, LP: 67858 - Should be doable. - Move eclipse bin to eclipse-platform.
- - Alternatively sort out eclipse's depends.
-
-Postponed:
-
diff --git a/debian/changelog b/debian/changelog
index b23ebd1..16632d5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,46 +10,40 @@ eclipse (3.5.1+repack-1) UNRELEASED; urgency=low
- Fixed build for various archs. (Closes: #521312)
* Stopped eclipse from unpacking native libraries into ~/.eclipse.
(Closes: #351729)
- * Corrected Depends and Recommends.
+ * Corrected Depends and Recommends. (Closes: #554677, #558246)
- eclipse-jdt now only suggests eclipse.
- removed strict dependency on openjdk.
- removed recommends on eclipse-*-gcj packages.
- (Closes: #554677, #558246)
* Removed obsolete linda overrides.
* New maintainers. (Closes: #526489)
* Removed the need for Zenity (Closes: #528070)
- * Added missing "apt" plug-in for eclipse-jdt.
- (Closes: #403655, LP: #120610)
- * Added conflicts on the old eclipse-*-nls packages.
- (Closes: #538869)
+ * Added missing "apt" plug-in for eclipse-jdt. (Closes: #403655, LP: #120610)
+ * Added conflicts on the old eclipse-*-nls packages. (Closes: #538869)
* Removed "builtin browser not supported"-warning; it did not work.
(Closes: #402340, #491542)
* Removed dependency on libtomcat5.5-java and liblucene-java-doc.
- * Stopped using special hacks and work arounds to find JVMs.
- (Closes: #353360)
+ * Stopped using special hacks and work arounds to find JVMs. (Closes: #353360)
- This removes the need for ~/.eclipse/eclipserc (Closes: #402077)
- This makes eclipse read eclipse.ini (Closes: #491334)
- * Moved the executable to eclipse-platform from eclipse.
- (Closes: #358594)
+ * Moved the executable to eclipse-platform from eclipse. (Closes: #358594)
* Put the osgi jar-files into its own separate package. (LP: #102717)
* Added workaround for gtk problems. (Closes: #552480)
* Added missing API references. (Closes: #376850)
* Moved org.eclipse.ant.ui to eclipse-platform. (LP: #477944)
- * Added information about how to create the orig.tar.gz.
- (Closes: #505553)
+ * Added information about how to create the orig.tar.gz. (Closes: #505553)
* Rewrote symlink script to handle folders that are renamed on different
archs/builds. (LP: #471859)
* Move eclipse.ini into /etc (LP: #43162)
* Set a sane file limit for osgi-bundles. (Closes: #558693, LP: #293573)
* Inject update sites on first run. (LP: #460944)
- * Prevent conflict with swt-gtk's swt packages.
+ * Prevent conflict with swt-gtk's swt packages. (Closes: #541638, LP: #491880)
- Removed our swt packages.
- Do not install conflicting symlinks/files.
- (Closes: #541638, LP: #491880)
- * Imported patch from Fedora that fixes seg. faults in libpango.
- (LP: #445009)
+ * Imported patch from Fedora that fixes seg. faults in libpango. (LP: #445009)
+ * Update manpage. (LP: #494065)
+ * Bump Standards-Version to 3.8.4.
- -- Debian Orbital Alignment Team <pkg-java-maintainers at lists.alioth.debian.org> Tue, 01 Dec 2009 20:28:17 +0100
+ -- Debian Orbital Alignment Team <pkg-java-maintainers at lists.alioth.debian.org> Sat, 30 Jan 2010 15:39:25 +0100
eclipse (3.4.1-1) unstable; urgency=low
diff --git a/debian/control b/debian/control
index 221110a..748ab19 100644
--- a/debian/control
+++ b/debian/control
@@ -10,6 +10,7 @@ Build-Depends: ant (>= 1.7.1),
cdbs,
debhelper (>= 7),
default-jdk,
+ docbook2x,
junit (>= 3.8.2-4),
junit4 (>= 4.7-3),
libatk1.0-dev,
@@ -40,7 +41,7 @@ Build-Depends: ant (>= 1.7.1),
unzip,
xulrunner-dev (>= 1.9.1),
zip
-Standards-Version: 3.8.3
+Standards-Version: 3.8.4
DM-Upload-Allowed: yes
Vcs-Git: git://git.debian.org/git/pkg-java/eclipse.git
Vcs-Browser: http://git.debian.org/?p=pkg-java/eclipse.git
@@ -117,7 +118,6 @@ Depends: default-jre | java1-runtime | java2-runtime | java5-runtime | java6-run
liblucene2-java (>= 2.9.1+ds1-5),
libservlet2.4-java (>= 5.0.30-10),
libservlet2.5-java (>= 6.0.20-8),
- libswt-eclipse-java (= ${binary:Version}),
sat4j (>= 2.1.0),
xulrunner-1.9.1,
${misc:Depends},
@@ -195,7 +195,6 @@ Architecture: any
Depends: default-jre | java1-runtime | java2-runtime | java5-runtime | java6-runtime,
libequinox-osgi-java (= ${source:Version}),
libicu4j-java (>= 4.0.1.1),
- libswt-eclipse-java (= ${binary:Version}),
${shlibs:Depends},
${misc:Depends}
Recommends: ${shlibs:Recommends}
diff --git a/debian/eclipse-platform.install b/debian/eclipse-platform.install
index c7d4195..e6f0f05 100644
--- a/debian/eclipse-platform.install
+++ b/debian/eclipse-platform.install
@@ -237,3 +237,4 @@ usr/lib/eclipse/plugins/org.sat4j.core_*.jar
usr/lib/eclipse/plugins/org.sat4j.pb_*.jar
usr/lib/eclipse/startup.jar
usr/share/applications
+usr/share/man
diff --git a/debian/eclipse-platform.manpages b/debian/eclipse-platform.manpages
deleted file mode 100644
index 860f078..0000000
--- a/debian/eclipse-platform.manpages
+++ /dev/null
@@ -1 +0,0 @@
-debian/extra/eclipse.1
diff --git a/debian/extra/eclipse.1 b/debian/extra/eclipse.1
deleted file mode 100644
index 99da649..0000000
--- a/debian/extra/eclipse.1
+++ /dev/null
@@ -1,226 +0,0 @@
-.TH ECLIPSE 1
-.SH NAME
-eclipse \- A kind of universal tool platform.
-.SH SYNOPSIS
-.B eclipse
-.I "[platform options]" "[\-vmargs [Java VM arguments]]"
-.SH "DESCRIPTION"
-.B Eclipse
-is a kind of universal tool platform - an open extensible IDE for anything and nothing in paticular.
-.PP
-This manual page documents briefly
-.BR Eclipse,
-a kind of universal tool platform.
-This manual page was written for the Debian GNU/Linux distribution
-because the original program does not have a manual page. Most of description are
-just cut and paste from Eclipse's document.
-
-.SH PLATFORM OPTIONS
-A summary of platform options are included below. Some of this options can
-be set by editing ~/.eclipse/eclipserc (but options given on the commandline
-will overwrite them). This is useful, when you start eclipse via menu entry.
-.TP
-.B \-arch <architecture>
-Defines 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".
-.TP
-.B \-application <applicationId>
-The 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.
-.TP
-.B \-clean
-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
-reinitialize these caches.
-.TP
-.B \-configuration <configurationFileURL>
-The 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 that relative
-URLs are not allowed. The configuration file is written to this location
-when the Eclipse platform is installed or updated.
-.TP
-.B \-console [port]
-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 the port on which
-the console listens and directs its output to the given port. Handy for
-investigating the state of the system.
-.TP
-.B \-consolelog
-Mirrors the Eclipse platform's error log to the console used to run Eclipse.
-Handy when combined with \-debug.
-.TP
-.B \-data <workspacePath>
-The 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.
-.TP
-.B \-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 called ".options". Both URLs and file system paths
-are allowed as file locations.
-.PP
-.B Note:
-On Debian, eclipse expects that the following arguments is a path to a
-option file. You are not allowed to omit this file!
-.TP
-.B \-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.
-.TP
-.B \-endSplash <command>
-Specifies the command to use to take down the splash screen. Typically
-supplied by the Eclipse executable.
-.TP
-.B \-feature <feature id>
-The identifier of the product being run. This controls various branding
-information and what application is used.
-.TP
-.B \-framework <location>
-The URL location of the OSGi framework. Useful if the Eclipse install is
-disjoint.
-.TP
-.B \-initialize
-Initializes the configuration being run. All runtime related data structures
-and caches are refreshed. Any user/plug-in defined configuration data is not
-purged. No application is run, any product specifications are ignored and no
-UI is presented (e.g., the splash screen is not drawn)
-.TP
-.B \-install <location>
-The install location of the platform. This setting indicates the location of
-the basic Eclipse plug-ins and is useful if the Eclipse install is disjoint.
-.TP
-.B \-keyring <keyringFilePath>
-The location of the authorization database (or "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.
-.TP
-.B \-name <string>
-The name to be displayed in task bar item when the application starts up. When
-not set, the name is the name of the executable.
-.TP
-.B \-nl <locale>
-Defines 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".
-.PP
-You need to install additonal language strings, before that works! Such
-strings are available in the
-.B eclipse-i18n
-package.
-.TP
-.B \-noExit
-The VM will not exit after the eclipse application has ended. This is useful
-for examining the OSGi framework after the eclipse application has ended.
-.TP
-.B \-noLazyRegistryCacheLoading
-The platform's plug-in registry cache loading optimization is deactivated.
-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.
-.TP
-.B \-noRegistryCache
-The internal extension registry cache is neither read or written
-.TP
-.B \-nosplash
-Runs the platform without putting up the splash screen.
-.TP
-.B \-os <operatingSystem>
-Defines 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. Example
-values: "win32", "linux", "hpux", "solaris", "aix".
-.TP
-.B \-password <password>
-The password for the authorization database. Used in conjunction with the
-\-keyring option.
-.TP
-.B \-perspective <perspectiveId>
-The 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.
-.TP
-.B \-plugincustomization <propertiesFile>
-The 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.
-.TP
-.B \-product <productId>
-The ID of the product to run. The product gives the launched instance of
-Eclipse its personality, and determines the product customization information
-used. This replaces \-feature, which is still supported for compatibility.
-.TP
-.B \-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.
-.TP
-.B \-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.
-.TP
-.B \-showSplash <command>
-Specifies the command to use to show the splash screen. Typically supplied
-by the Eclipse executable.
-.TP
-.B \-startup <location>
-The location of jar used to startup eclipse. The jar referred to must have
-the Main-Class attribute set. If this parameter is not set, the startup.jar
-located in the same folder than the executable is used.
-.TP
-.B \-user <location>
-The location of the user area. The user area contains data (e.g., preferences)
-specific to the OS user and independent of any Eclipse install, configuration
-or instance.
-.TP
-.B \-vm <vmPath>
-The location of Java Runtime executable to use to run the Eclipse platform.
-Relative paths are interpreted relative to the directory that eclipse was
-started from.
-.TP
-.B \-vmargs <args>
-When passed to the Eclipse, this option is used to customize the operation of
-the Java VM used to run Eclipse. If specified, this option must come at the
-end of the command line. The given arguments are dependent on VM that is
-being run.
-.TP
-.B \-ws <window system>
-The window system value. The value should be one of the Eclipse window system
-names known to Eclipse (e.g., win32, motif, ...).
-.SH NOTES
-Eclipse will search for a java virtual machine in this order: VM given with
-the "\-vm <JVM>" argument, $JAVA_HOME/bin/java from $HOME/.eclipse/eclipserc
-and then in the environment and at last use /usr/bin/java.
-.SH SEE ALSO
-java(1)
-.SH FILES
-Configuration file is $HOME/.eclipse/eclipserc, error log in
-<workspace>/.metadata/.log, where <workspace> is the path to your workspace.
-.SH BUGS
-Eclipse has a bugzilla, which can be found at bugs.eclipse.org.
-.SH AUTHOR
-This manual page was written by Takashi Okamoto <tora at debian.org>,
-for the Debian GNU/Linux system (but may be used by others). It was updated
-by Jan Schulz <debian at katzien.de> and Stephan Michels <stephan at apache.org>.
diff --git a/debian/patches/eclipse-manpage.patch b/debian/patches/eclipse-manpage.patch
new file mode 100644
index 0000000..23e14e5
--- /dev/null
+++ b/debian/patches/eclipse-manpage.patch
@@ -0,0 +1,577 @@
+Description: Add eclipse manpage
+Author: Benjamin Drung <bdrung at ubuntu.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 @@
++<?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 -->
++<refentry id='eclipse1'>
++<refmeta>
++<refentrytitle>eclipse</refentrytitle>
++<manvolnum>1</manvolnum>
++</refmeta>
++<refnamediv id='name'>
++<refname>eclipse</refname>
++<refpurpose>extensible tool platform and Java IDE</refpurpose>
++</refnamediv>
++<!-- body begins here -->
++<refsynopsisdiv id='synopsis'>
++<cmdsynopsis>
++ <command>eclipse</command>
++ <arg choice='opt'><arg choice='plain'><replaceable>platform</replaceable></arg><arg choice='plain'><replaceable>options</replaceable></arg></arg>
++ <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>
++</cmdsynopsis>
++</refsynopsisdiv>
++
++
++<refsect1 id='description'><title>DESCRIPTION</title>
++<para>
++The <command>Eclipse</command> Platform is an open and
++ extensible platform for anything and yet nothing in particular. It provides a
++ foundation for constructing and running integrated software-development tools.
++ The <command>Eclipse</command> Platform allows tool builders
++ to independently develop tools that integrate with other people's tools so
++ seamlessly you can't tell where one tool ends and another starts.</para>
++
++ <para>When invoked without selecting any particular application, the <command>eclipse</command>
++ command will start the <command>Eclipse</command> Platform with the Java Development
++ Tools (JDT) functionality enabled and ready to use.</para>
++
++<para>This manual page documents the command-line arguments for the
++<command>Eclipse</command> Platform and it is based on the
++Runtime Options help item in the <command>Eclipse</command>
++<ulink url="#authors" xrefstyle="AUTHORS">online help</ulink><!-- (see xref endterm="authors" linkend="authors" xrefstyle="AUTHORS"></xref> AUTHORS below)-->.</para>
++
++</refsect1>
++
++<refsect1 id='platform_options'><title>PLATFORM OPTIONS</title>
++<para> Listed below are the command line arguments processed by various parts of the
++<command>Eclipse</command> runtime.
++Many of these values can also be specified using System properties either on the command line
++using <command>-D VM</command> arguments, by specifying their values in a <filename>config.ini</filename> file or by using a
++<filename><launcher>.ini</filename> file. Using the two latter techniques it is possible to customize
++<command>Eclipse</command> without using command line arguments at all.</para>
++
++<para>For each argument in the list, its corresponding System property key is given (in {}). Also
++given is the <command>Eclipse</command> runtime layer in which the
++command line argument is processed (in ()). </para>
++
++<variablelist remap='TP'>
++
++<varlistentry>
++ <term><option>
++ -application <id> (Runtime)
++ </option></term>
++ <listitem>
++ <para>
++ The identifier of the application to run. The value given here
++ overrides any application defined by the product being run</para>
++ <para>
++ This is equivalent to setting the property
++ <emphasis>eclipse.application</emphasis> to
++ <id>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -arch <architecture> (OSGi)
++ </option></term>
++ <listitem>
++ <para>The processor architecture value.</para>
++ <para>
++ This is equivalent to setting the property <emphasis>osgi.arch</emphasis> to
++ <architecture>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -clean (OSGi)
++ </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
++ reinitialize these caches.
++ </para>
++ <para>
++ This is equivalent to setting the property <emphasis>osgi.clean</emphasis> to
++ "true".
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -configuration <location> (Main)
++ </option></term>
++ <listitem>
++ <para>The configuration location for this run of the platform. The
++ configuration determines what plug-ins will run as well as various
++ other system settings. See the On-line Help for details (SEE ALSO below).</para>
++ <para>
++ This is equivalent to setting the property <emphasis>osgi.configuration.area</emphasis>
++ to <location>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -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
++ 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>
++ This is equivalent to setting the property <emphasis>osgi.console</emphasis> to [port] or the
++ empty string if the default port is to be used (i.e., when the port is not specified).
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -consoleLog (Runtime)
++ </option></term>
++ <listitem>
++ <para>If "true", 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>
++ <para>
++ This is equivalent to setting the property <emphasis>eclipse.consoleLog</emphasis> to
++ "true".
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -data <location> (OSGi)<literallayout></literallayout>
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property <emphasis>osgi.instance.area</emphasis> to
++ <location>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -debug [options file] (OSGi)
++ </option></term>
++ <listitem>
++ <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
++ the options file location is not specified).
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -dev [entries] (OSGi)
++ </option></term>
++ <listitem>
++ <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
++ entries are not specified).
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -eclipse.keyring <file path> (Equinox)
++ </option></term>
++ <listitem>
++ <para>
++ Set to override location of the default secure storage.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -eclipse.password <file path> (Equinox)
++ </option></term>
++ <listitem>
++ <para>
++ If specified, the secure storage treats contents of the file as a
++ default password. When not set, password providers are used to
++ obtain a password.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -feature <feature id> (Runtime)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property <emphasis>eclipse.product</emphasis> to <feature
++ id>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -framework <location> (Main)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property <emphasis>osgi.framework</emphasis> to
++ <location>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -initialize (Main)
++ </option></term>
++ <listitem>
++ <para>
++ Initializes the configuration being run. All runtime related data
++ structures and caches are refreshed. Any user/plug-in defined
++ configuration data is not purged. No application is run, any
++ product specifications are ignored and no UI is presented (e.g.,
++ the splash screen is not drawn).
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -install <location> (Main)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property <emphasis>osgi.install.area</emphasis> to
++ <location>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -keyring <location> (Runtime)
++ </option></term>
++ <listitem>
++ <para>
++ The location of the authorization database on disk. This argument
++ has to be used together with the -password argument.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ --launcher.library <location> (Executable)
++ </option></term>
++ <listitem>
++ <para>
++ The location of the eclipse 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.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ --launcher.ini <location> (Executable)
++ </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).
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ --launcher.suppressErrors (Executable)
++ </option></term>
++ <listitem>
++ <para>
++ If specified the executable will not display any error or message
++ dialogs. This is useful if the executable is being used in an
++ unattended situation.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ --launcher.XXMaxPermSize <value> (Executable)
++ </option></term>
++ <listitem>
++ <para>
++ If specified, and the executable detects that the VM being used is
++ 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>
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -name <string>
++ </option></term>
++ <listitem>
++ <para>
++ The name to be displayed in task bar item when the application
++ starts up. When not set, the name is the name of the executable.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -nl <locale> (OSGi)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property
++ <emphasis>osgi.nl</emphasis> to
++ <locale>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -noExit (OSGi)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property
++ <emphasis>osgi.noShutdown</emphasis> to
++ "true".
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -noLazyRegistryCacheLoading (Runtime)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property
++ <emphasis>eclipse.noLazyRegistryCacheLoading</emphasis>
++ to "true".
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -noRegistryCache (Runtime)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property
++ <emphasis>eclipse.noRegistryCache</emphasis>
++ to "true".
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -noSplash (Executable, Main)
++ </option></term>
++ <listitem>
++ <para>
++ Controls whether or not the splash screen is shown.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -os <operating system> (OSGi)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property
++ <emphasis>osgi.os</emphasis> to
++ <operating system>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -password <password> (Runtime)
++ </option></term>
++ <listitem>
++ <para>
++ The password for the authorization database.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -pluginCustomization <location> (Runtime)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property
++ <emphasis>eclipse.pluginCustomization</emphasis>
++ to <location>
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -product <id> (OSGi)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property
++ <emphasis>eclipse.product</emphasis> to <id>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -showSplash <bitmap> (Executable, Main)
++ </option></term>
++ <listitem>
++ <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
++ the <emphasis>osgi.splashLocation</emphasis> and <emphasis>osgi.splashPath</emphasis>
++ properties.<literallayout></literallayout>
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -startup <location> (Executable)
++ </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 executable will look in the plugins directory for
++ theorg.eclipse.equinox.launcher bundle with the highest
++ version.<literallayout></literallayout>
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -user <location> (OSGi)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property
++ <emphasis>osgi.user.area</emphasis> to
++ <location>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -vm <path to java vm> (Executable, Main)
++ </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
++ VM Execution Environment description file. If not specified,
++ the Eclipse 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
++ this value in <emphasis>eclipse.vm</emphasis>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -vmargs [vmargs*] (Executable, Main)
++ </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
++ 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
++ argument. Java Main then stores this value in
++ <emphasis>eclipse.vmargs</emphasis>.
++ </para>
++ </listitem>
++ </varlistentry>
++ <varlistentry>
++ <term><option>
++ -ws <window system> (OSGi)
++ </option></term>
++ <listitem>
++ <para>
++ This is equivalent to setting the property
++ <emphasis>osgi.ws</emphasis> to
++ <window system>.
++ </para>
++ </listitem>
++ </varlistentry>
++
++ </variablelist>
++</refsect1>
++
++<refsect1 id='see_also'><title>SEE ALSO</title>
++<para><citerefentry><refentrytitle>java</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
++<citerefentry><refentrytitle>ecj</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
++<para><command>Eclipse</command> On-line Help <ulink url='http://help.eclipse.org/'>http://help.eclipse.org/</ulink>
++<glossterm>Platform Plug-in Developer Guide</glossterm> > <glossterm>Reference</glossterm> > <glossterm>Other reference information</glossterm> >
++<glossterm>Runtime Options</glossterm>.</para>
++
++</refsect1>
++
++<refsect1 id='files'><title>FILES</title>
++<para>The system wide config.ini file is <filename>/etc/eclipse.ini</filename>. User level Configuration file is
++<filename>$HOME/.eclipse/org.eclipse.platform_<version>_<id>/configuration/config.ini</filename>.</para>
++</refsect1>
++
++<refsect1 XrefLabel="AUTHORS" id="authors"><title>AUTHORS</title>
++<para>
++The <command>Eclipse</command> Project was originally created by IBM in November 2001 and
++supported by a consortium of software vendors. The <command>Eclipse</command> Foundation was
++created in January 2004 as an independent not-for-profit corporation to act as the steward of the
++<command>Eclipse</command> community.
++</para>
++<para>This manual page was semi-automatically transformed from the
++Runtime Options HTML help using <command>pandoc</command> and
++<command>docbook2x-man</command> by Pablo Duboue <pablo.duboue at gmail.com>.</para>
++
++</refsect1>
++</refentry>
diff --git a/debian/patches/series b/debian/patches/series
index cab9909..4997a2a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -8,3 +8,4 @@ lucene.patch
swtbug291128.patch
source-jars.patch
install-icu4j-bundles.patch
+eclipse-manpage.patch
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 @@
+<?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 -->
+<refentry id='eclipse1'>
+<refmeta>
+<refentrytitle>eclipse</refentrytitle>
+<manvolnum>1</manvolnum>
+</refmeta>
+<refnamediv id='name'>
+<refname>eclipse</refname>
+<refpurpose>extensible tool platform and Java IDE</refpurpose>
+</refnamediv>
+<!-- body begins here -->
+<refsynopsisdiv id='synopsis'>
+<cmdsynopsis>
+ <command>eclipse</command>
+ <arg choice='opt'><arg choice='plain'><replaceable>platform</replaceable></arg><arg choice='plain'><replaceable>options</replaceable></arg></arg>
+ <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>
+</cmdsynopsis>
+</refsynopsisdiv>
+
+
+<refsect1 id='description'><title>DESCRIPTION</title>
+<para>
+The <command>Eclipse</command> Platform is an open and
+ extensible platform for anything and yet nothing in particular. It provides a
+ foundation for constructing and running integrated software-development tools.
+ The <command>Eclipse</command> Platform allows tool builders
+ to independently develop tools that integrate with other people's tools so
+ seamlessly you can't tell where one tool ends and another starts.</para>
+
+ <para>When invoked without selecting any particular application, the <command>eclipse</command>
+ command will start the <command>Eclipse</command> Platform with the Java Development
+ Tools (JDT) functionality enabled and ready to use.</para>
+
+<para>This manual page documents the command-line arguments for the
+<command>Eclipse</command> Platform and it is based on the
+Runtime Options help item in the <command>Eclipse</command>
+<ulink url="#authors" xrefstyle="AUTHORS">online help</ulink><!-- (see xref endterm="authors" linkend="authors" xrefstyle="AUTHORS"></xref> AUTHORS below)-->.</para>
+
+</refsect1>
+
+<refsect1 id='platform_options'><title>PLATFORM OPTIONS</title>
+<para> Listed below are the command line arguments processed by various parts of the
+<command>Eclipse</command> runtime.
+Many of these values can also be specified using System properties either on the command line
+using <command>-D VM</command> arguments, by specifying their values in a <filename>config.ini</filename> file or by using a
+<filename><launcher>.ini</filename> file. Using the two latter techniques it is possible to customize
+<command>Eclipse</command> without using command line arguments at all.</para>
+
+<para>For each argument in the list, its corresponding System property key is given (in {}). Also
+given is the <command>Eclipse</command> runtime layer in which the
+command line argument is processed (in ()). </para>
+
+<variablelist remap='TP'>
+
+<varlistentry>
+ <term><option>
+ -application <id> (Runtime)
+ </option></term>
+ <listitem>
+ <para>
+ The identifier of the application to run. The value given here
+ overrides any application defined by the product being run</para>
+ <para>
+ This is equivalent to setting the property
+ <emphasis>eclipse.application</emphasis> to
+ <id>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -arch <architecture> (OSGi)
+ </option></term>
+ <listitem>
+ <para>The processor architecture value.</para>
+ <para>
+ This is equivalent to setting the property <emphasis>osgi.arch</emphasis> to
+ <architecture>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -clean (OSGi)
+ </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
+ reinitialize these caches.
+ </para>
+ <para>
+ This is equivalent to setting the property <emphasis>osgi.clean</emphasis> to
+ "true".
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -configuration <location> (Main)
+ </option></term>
+ <listitem>
+ <para>The configuration location for this run of the platform. The
+ configuration determines what plug-ins will run as well as various
+ other system settings. See the On-line Help for details (SEE ALSO below).</para>
+ <para>
+ This is equivalent to setting the property <emphasis>osgi.configuration.area</emphasis>
+ to <location>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -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
+ 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>
+ This is equivalent to setting the property <emphasis>osgi.console</emphasis> to [port] or the
+ empty string if the default port is to be used (i.e., when the port is not specified).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -consoleLog (Runtime)
+ </option></term>
+ <listitem>
+ <para>If "true", 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>
+ <para>
+ This is equivalent to setting the property <emphasis>eclipse.consoleLog</emphasis> to
+ "true".
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -data <location> (OSGi)<literallayout></literallayout>
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property <emphasis>osgi.instance.area</emphasis> to
+ <location>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -debug [options file] (OSGi)
+ </option></term>
+ <listitem>
+ <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
+ the options file location is not specified).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -dev [entries] (OSGi)
+ </option></term>
+ <listitem>
+ <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
+ entries are not specified).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -eclipse.keyring <file path> (Equinox)
+ </option></term>
+ <listitem>
+ <para>
+ Set to override location of the default secure storage.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -eclipse.password <file path> (Equinox)
+ </option></term>
+ <listitem>
+ <para>
+ If specified, the secure storage treats contents of the file as a
+ default password. When not set, password providers are used to
+ obtain a password.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -feature <feature id> (Runtime)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property <emphasis>eclipse.product</emphasis> to <feature
+ id>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -framework <location> (Main)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property <emphasis>osgi.framework</emphasis> to
+ <location>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -initialize (Main)
+ </option></term>
+ <listitem>
+ <para>
+ Initializes the configuration being run. All runtime related data
+ structures and caches are refreshed. Any user/plug-in defined
+ configuration data is not purged. No application is run, any
+ product specifications are ignored and no UI is presented (e.g.,
+ the splash screen is not drawn).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -install <location> (Main)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property <emphasis>osgi.install.area</emphasis> to
+ <location>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -keyring <location> (Runtime)
+ </option></term>
+ <listitem>
+ <para>
+ The location of the authorization database on disk. This argument
+ has to be used together with the -password argument.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ --launcher.library <location> (Executable)
+ </option></term>
+ <listitem>
+ <para>
+ The location of the eclipse 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.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ --launcher.ini <location> (Executable)
+ </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).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ --launcher.suppressErrors (Executable)
+ </option></term>
+ <listitem>
+ <para>
+ If specified the executable will not display any error or message
+ dialogs. This is useful if the executable is being used in an
+ unattended situation.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ --launcher.XXMaxPermSize <value> (Executable)
+ </option></term>
+ <listitem>
+ <para>
+ If specified, and the executable detects that the VM being used is
+ 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>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -name <string>
+ </option></term>
+ <listitem>
+ <para>
+ The name to be displayed in task bar item when the application
+ starts up. When not set, the name is the name of the executable.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -nl <locale> (OSGi)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property
+ <emphasis>osgi.nl</emphasis> to
+ <locale>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -noExit (OSGi)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property
+ <emphasis>osgi.noShutdown</emphasis> to
+ "true".
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -noLazyRegistryCacheLoading (Runtime)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property
+ <emphasis>eclipse.noLazyRegistryCacheLoading</emphasis>
+ to "true".
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -noRegistryCache (Runtime)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property
+ <emphasis>eclipse.noRegistryCache</emphasis>
+ to "true".
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -noSplash (Executable, Main)
+ </option></term>
+ <listitem>
+ <para>
+ Controls whether or not the splash screen is shown.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -os <operating system> (OSGi)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property
+ <emphasis>osgi.os</emphasis> to
+ <operating system>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -password <password> (Runtime)
+ </option></term>
+ <listitem>
+ <para>
+ The password for the authorization database.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -pluginCustomization <location> (Runtime)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property
+ <emphasis>eclipse.pluginCustomization</emphasis>
+ to <location>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -product <id> (OSGi)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property
+ <emphasis>eclipse.product</emphasis> to <id>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -showSplash <bitmap> (Executable, Main)
+ </option></term>
+ <listitem>
+ <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
+ the <emphasis>osgi.splashLocation</emphasis> and <emphasis>osgi.splashPath</emphasis>
+ properties.<literallayout></literallayout>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -startup <location> (Executable)
+ </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 executable will look in the plugins directory for
+ theorg.eclipse.equinox.launcher bundle with the highest
+ version.<literallayout></literallayout>
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -user <location> (OSGi)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property
+ <emphasis>osgi.user.area</emphasis> to
+ <location>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -vm <path to java vm> (Executable, Main)
+ </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
+ VM Execution Environment description file. If not specified,
+ the Eclipse 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
+ this value in <emphasis>eclipse.vm</emphasis>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -vmargs [vmargs*] (Executable, Main)
+ </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
+ 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
+ argument. Java Main then stores this value in
+ <emphasis>eclipse.vmargs</emphasis>.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>
+ -ws <window system> (OSGi)
+ </option></term>
+ <listitem>
+ <para>
+ This is equivalent to setting the property
+ <emphasis>osgi.ws</emphasis> to
+ <window system>.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ </variablelist>
+</refsect1>
+
+<refsect1 id='see_also'><title>SEE ALSO</title>
+<para><citerefentry><refentrytitle>java</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
+<citerefentry><refentrytitle>ecj</refentrytitle><manvolnum>1</manvolnum></citerefentry>.</para>
+<para><command>Eclipse</command> On-line Help <ulink url='http://help.eclipse.org/'>http://help.eclipse.org/</ulink>
+<glossterm>Platform Plug-in Developer Guide</glossterm> > <glossterm>Reference</glossterm> > <glossterm>Other reference information</glossterm> >
+<glossterm>Runtime Options</glossterm>.</para>
+
+</refsect1>
+
+<refsect1 id='files'><title>FILES</title>
+<para>The system wide config.ini file is <filename>/etc/eclipse.ini</filename>. User level Configuration file is
+<filename>$HOME/.eclipse/org.eclipse.platform_<version>_<id>/configuration/config.ini</filename>.</para>
+</refsect1>
+
+<refsect1 XrefLabel="AUTHORS" id="authors"><title>AUTHORS</title>
+<para>
+The <command>Eclipse</command> Project was originally created by IBM in November 2001 and
+supported by a consortium of software vendors. The <command>Eclipse</command> Foundation was
+created in January 2004 as an independent not-for-profit corporation to act as the steward of the
+<command>Eclipse</command> community.
+</para>
+<para>This manual page was semi-automatically transformed from the
+Runtime Options HTML help using <command>pandoc</command> and
+<command>docbook2x-man</command> by Pablo Duboue <pablo.duboue at gmail.com>.</para>
+
+</refsect1>
+</refentry>
hooks/post-receive
--
eclipse - Powerful IDE written in java - Debian package.
More information about the pkg-java-commits
mailing list