diff options
| author | Sebastian Ratz | 2019-04-08 13:47:02 +0000 |
|---|---|---|
| committer | Matthias Becker | 2019-04-08 15:08:38 +0000 |
| commit | ef9f739262dfbb4e3a7aec2f8914a4ea2e5fc676 (patch) | |
| tree | bca240f9b28a7fe24114ac9c446f1be7d9d8d122 | |
| parent | b9219a178ce81f0e6189d21a73f76336a7b7fc6b (diff) | |
| download | eclipse.platform.common-ef9f739262dfbb4e3a7aec2f8914a4ea2e5fc676.tar.gz eclipse.platform.common-ef9f739262dfbb4e3a7aec2f8914a4ea2e5fc676.tar.xz eclipse.platform.common-ef9f739262dfbb4e3a7aec2f8914a4ea2e5fc676.zip | |
Bug 545790 - Link handler for URI scheme cannot be added if
"eclipse.launcher" property is not set
Add note to documentation.
Change-Id: Ie391343d800552d7be877352168b4ecb8989ebf7
Signed-off-by: Sebastian Ratz <sebastian.ratz@sap.com>
| -rw-r--r-- | bundles/org.eclipse.platform.doc.user/reference/ref-linkhandlersprefs.htm | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/bundles/org.eclipse.platform.doc.user/reference/ref-linkhandlersprefs.htm b/bundles/org.eclipse.platform.doc.user/reference/ref-linkhandlersprefs.htm index a92d2ba88..2a43338be 100644 --- a/bundles/org.eclipse.platform.doc.user/reference/ref-linkhandlersprefs.htm +++ b/bundles/org.eclipse.platform.doc.user/reference/ref-linkhandlersprefs.htm @@ -35,6 +35,7 @@ <li>The enabled state of each URL scheme is not persisted in the Eclipse preference store, but it is directly registered in the operating system. Therefore, this page does not take part in the export and import of preferences and does not provide a "Restore Defaults" button.</li> <li>For the "macOS" and "Linux" operating system: If an URL scheme is handled by another application (Eclipse-based or not), it <strong>cannot</strong> be enabled directly. Handling of this URL scheme must first be disabled in the other application, before it can be enabled in the current application.</li> <li>When multiple Eclipse-based applications are running at the same time, the operating system may set a window to the foreground, which cannot handle the link. In such cases, ensure that only the expected Eclipse-based application is running.</li> + <li>In rare cases (e.g. PDE development) the path to the eclipse launcher can not be determined from the <code>eclipse.launcher</code> or <code>eclipse.home.location</code> system properties. The preference page will then show an error message and will not allow any interaction.</li> </ul> </body> </html> |