|
Lines 1063-1083
Link Here
|
| 1063 |
means the server is using a self-signed certificate, or a certificate authenticated by |
1063 |
means the server is using a self-signed certificate, or a certificate authenticated by |
| 1064 |
an unknown third party.</p> |
1064 |
an unknown third party.</p> |
| 1065 |
|
1065 |
|
| 1066 |
<h4>Removing a link file does not uninstall the corresponding extension location</h4> |
1066 |
<h4>Extension location is lost if the install path changes</h4> |
| 1067 |
<p>If you have an extension location in an Eclipse-based application that is connected |
|
|
| 1068 |
to your configuration via a link file, the extension is not removed when the link is deleted. |
| 1069 |
The workaround is to move or delete the extension location, and restart the platform |
| 1070 |
with the -clean command line argument. You can then restore or move back the |
| 1071 |
extension location content to its original location (bug <A HREF="https://bugs.eclipse.org/bugs/show_bug.cgi?id=232094">232094</A>). |
| 1072 |
</p> |
| 1073 |
|
| 1074 |
<p><B>Extension location is lost if the install path changes</B></p> |
| 1075 |
<P>A previously configured extension location may be temporarily removed if the install is moved or mounted |
1067 |
<P>A previously configured extension location may be temporarily removed if the install is moved or mounted |
| 1076 |
under a different path. This only happens when the link file that configures the |
1068 |
under a different path. This only happens when the link file that configures the |
| 1077 |
extension location uses a relative path that points to a directory under the Eclipse |
1069 |
extension location uses a relative path that points to a directory under the Eclipse |
| 1078 |
install. On a second startup using the same install path, the extension location |
1070 |
install. On a second startup using the same install path, the extension location |
| 1079 |
is added again (bug <A HREF="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95403">95403</A>). <BR></P> |
1071 |
is added again (bug <A HREF="https://bugs.eclipse.org/bugs/show_bug.cgi?id=95403">95403</A>). <BR></P> |
| 1080 |
|
1072 |
|
|
|
1073 |
<h4>Feature patches can only be installed from Eclipse 3.4-based update sites</h4> |
| 1074 |
<p>Feature patches can only be installed from update sites designed for Eclipse 3.4 or greater. |
| 1075 |
Specifically, the update site must have the necessary metadata for Equinox p2 (a content.xml |
| 1076 |
or content.jar file). This data can be generated by building an update site using Eclipse 3.4 |
| 1077 |
or newer, or running the p2 metadata generator on an update site built using earlier versions |
| 1078 |
of the Eclipse SDK. See the help topic <i>Generating p2 metadata</i> for more details on running the p2 metadata |
| 1079 |
generator (bug <A HREF="https://bugs.eclipse.org/bugs/show_bug.cgi?id=244483">244483</A>). |
| 1080 |
</p> |
| 1081 |
|
| 1081 |
<h3>3.2.9 <a name="I-Platform-Debug">Platform - Debug</a></h3> |
1082 |
<h3>3.2.9 <a name="I-Platform-Debug">Platform - Debug</a></h3> |
| 1082 |
<p>None. (Known problems with the Java debugger appear below in the <a href="#I-JDT">JDT</a> |
1083 |
<p>None. (Known problems with the Java debugger appear below in the <a href="#I-JDT">JDT</a> |
| 1083 |
section.)</p> |
1084 |
section.)</p> |
