Bug 576463 -
http://www.eclipse.org/eclipse/development/porting/eclipse_4_21_porting_guide.html
is a 404 (and should be https)
Change-Id: If891276394d6c1158ee351cf64b8080e6d111970
Signed-off-by: Kalyan Prasad Tatavarthi <kalyan_prasad@in.ibm.com>
diff --git a/development/porting/eclipse_4_20_porting_guide.html b/development/porting/eclipse_4_20_porting_guide.html
index 5909933..e6b61fd 100644
--- a/development/porting/eclipse_4_20_porting_guide.html
+++ b/development/porting/eclipse_4_20_porting_guide.html
@@ -26,11 +26,11 @@
These documents describe those areas and provide instructions for migrating 4.19 plug-ins to
4.20.</p>
<ul>
- <li><a href="http://git.eclipse.org/c/platform/eclipse.platform.common.git/plain/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_x_porting_guide.html">
+ <li><a href="https://help.eclipse.org/2021-06/topic/org.eclipse.platform.doc.isv/porting/eclipse_4_20_porting_guide.html?cp=2_3_1_0">
Eclipse Platform 2021-06 (4.20) Plug-in Migration Guide</a></li>
- <li><a href="http://git.eclipse.org/c/platform/eclipse.platform.common.git/plain/bundles/org.eclipse.platform.doc.isv/porting/removals.html">
+ <li><a href="https://help.eclipse.org/2021-06/topic/org.eclipse.platform.doc.isv/porting/removals.html?cp=2_3_0">
Deprecated API removals in Eclipse Platform</a></li>
- <li><a href="http://git.eclipse.org/c/platform/eclipse.platform.common.git/plain/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_4_x_porting_guide.html">
+ <li><a href="https://help.eclipse.org/2021-06/topic/org.eclipse.jdt.doc.isv/porting/eclipse_4_20_porting_guide.html?cp=3_2_0_0">
Eclipse JDT 2021-06 (4.20) Plug-in Migration Guide</a></li>
</ul>
diff --git a/development/porting/eclipse_4_21_porting_guide.html b/development/porting/eclipse_4_21_porting_guide.html
new file mode 100644
index 0000000..f940072
--- /dev/null
+++ b/development/porting/eclipse_4_21_porting_guide.html
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html lang="en">
+<head>
+<meta name="copyright" content="Copyright (c) IBM Corporation and others 2021. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
+<meta http-equiv="Content-Style-Type" content="text/css">
+<link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
+<title>Eclipse 2021-09 (4.21) Plug-in Migration Guide</title>
+</head>
+
+<body>
+
+<h1>Eclipse 2021-09 (4.21) Plug-in Migration Guide</h1>
+<p>This guide covers migrating Eclipse 4.20 plug-ins to Eclipse 4.21.</p>
+<p>One of the goals of Eclipse 4.21 was to move Eclipse forward while remaining compatible
+ with previous versions to the greatest extent possible. That is, plug-ins written
+ against the Eclipse 4.20 APIs should continue to work in 4.21 in spite of any API changes.</p>
+<p>The key kinds of compatibility are API contract compatibility and binary compatibility.
+ API contract compatibility means that valid use of 4.20 APIs remains valid for
+ 4.21, so there is no need to revisit working code. Binary compatibility means
+ that the API method signatures, etc. did not change in ways that would cause
+ existing compiled ("binary") code to no longer link and run with the
+ new 4.21 libraries.</p>
+<p>While every effort was made to avoid breakage, there are a few areas of incompatibility or new
+ APIs that should be adopted by clients.
+ These documents describe those areas and provide instructions for migrating 4.20 plug-ins to
+ 4.21.</p>
+<ul>
+ <li><a href="https://help.eclipse.org/2021-09/topic/org.eclipse.platform.doc.isv/porting/eclipse_4_21_porting_guide.html?cp=2_3_1_0">
+ Eclipse Platform 2021-09 (4.21) Plug-in Migration Guide</a></li>
+ <li><a href="https://help.eclipse.org/2021-09/topic/org.eclipse.platform.doc.isv/porting/removals.html?cp=2_3_0">
+ Deprecated API removals in Eclipse Platform</a></li>
+ <li><a href="https://help.eclipse.org/2021-09/topic/org.eclipse.jdt.doc.isv/porting/eclipse_4_21_porting_guide.html?cp=3_2_0_0">
+ Eclipse JDT 2021-09 (4.21) Plug-in Migration Guide</a></li>
+</ul>
+
+</body>
+</html>
diff --git a/development/readme_eclipse_4.21.html b/development/readme_eclipse_4.21.html
index e475b3a..f077885 100644
--- a/development/readme_eclipse_4.21.html
+++ b/development/readme_eclipse_4.21.html
@@ -203,7 +203,7 @@
</p>
<p>
Eclipse 4.21 is tested and validated on a number of reference platforms. For the complete list, see <a
- href="https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_21.xml#target_environments">Target Environments in the
+ href="https://www.eclipse.org/projects/project-plan.php?planurl=https://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_21.xml#target_environments">Target Environments in the
4.21 Plan</a>.
</p>
<p>
@@ -234,20 +234,20 @@
<a
class="mozTocH3"
name="mozTocId324309"> <strong>API Contract Compatibility:</strong> Eclipse SDK 4.21 is upwards contract-compatible with Eclipse SDK 4.20 except in those areas noted in the
- </a><a href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_21_porting_guide.html"><em>Eclipse 4.21 Plug-in Migration Guide</em></a>. Programs that use affected APIs and extension points
+ </a><a href="https://www.eclipse.org/eclipse/development/porting/eclipse_4_21_porting_guide.html"><em>Eclipse 4.21 Plug-in Migration Guide</em></a>. Programs that use affected APIs and extension points
will need to be ported to Eclipse SDK 4.21 APIs. Downward contract compatibility is not supported. There is no guarantee that compliance with Eclipse SDK 4.21 APIs would ensure compliance with
Eclipse SDK 4.20 APIs. Refer to <a href="https://wiki.eclipse.org/Evolving_Java-based_APIs"><em>Evolving Java-based APIs</em></a> for a discussion of the kinds of API changes that maintain contract
compatibility.
</p>
<p>
<strong>Binary (plug-in) Compatibility:</strong> Eclipse SDK 4.21 is upwards binary-compatible with Eclipse SDK 4.20 except in those areas noted in the <a
- href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_21_porting_guide.html"><em>Eclipse 4.21 Plug-in Migration Guide</em> </a>. Downward plug-in compatibility is not supported.
+ href="https://www.eclipse.org/eclipse/development/porting/eclipse_4_21_porting_guide.html"><em>Eclipse 4.21 Plug-in Migration Guide</em> </a>. Downward plug-in compatibility is not supported.
Plug-ins for Eclipse SDK 4.21 will not be usable in Eclipse SDK 4.20. Refer to <a href="https://wiki.eclipse.org/Evolving_Java-based_APIs"> <em>Evolving Java-based APIs</em></a> for a discussion of
the kinds of API changes that maintain binary compatibility.
</p>
<p>
<strong>Source Compatibility:</strong> Eclipse SDK 4.21 is upwards source-compatible with Eclipse SDK 4.20 except in the areas noted in the <a
- href="http://www.eclipse.org/eclipse/development/porting/eclipse_4_21_porting_guide.html"><em>Eclipse 4.21 Plug-in Migration Guide</em> </a>. This means that source files written to use Eclipse
+ href="https://www.eclipse.org/eclipse/development/porting/eclipse_4_21_porting_guide.html"><em>Eclipse 4.21 Plug-in Migration Guide</em> </a>. This means that source files written to use Eclipse
SDK 4.21 APIs might successfully compile and run against Eclipse SDK 4.20 APIs, although this is not guaranteed. Downward source compatibility is not supported. If source files use new Eclipse SDK
APIs, they will not be usable with an earlier version of the Eclipse SDK.
</p>
@@ -403,8 +403,8 @@
name="mozTocId148479">To download Eclipse, try one of the links below:</a>
</p>
<ul>
- <li><a href="http://www.eclipse.org/downloads/">http://www.eclipse.org/downloads/</a></li>
- <li><a href="http://download.eclipse.org/eclipse/downloads/">http://download.eclipse.org/eclipse/downloads/</a></li>
+ <li><a href="https://www.eclipse.org/downloads/">https://www.eclipse.org/downloads/</a></li>
+ <li><a href="https://download.eclipse.org/eclipse/downloads/">https://download.eclipse.org/eclipse/downloads/</a></li>
</ul>
<p>
It is imperative that 64-bit builds are downloaded and used if a 64-bit Java runtime environment has been installed. Below is a sample tarball names of version 4.21 of the Eclipse SDK packaged
@@ -437,7 +437,7 @@
</code>
</p>
<p>
- Note that every argument must be on its own line. More information about the eclipse.ini file can be found at <a href="http://wiki.eclipse.org/Eclipse.ini">http://wiki.eclipse.org/Eclipse.ini</a>.
+ Note that every argument must be on its own line. More information about the eclipse.ini file can be found at <a href="https://wiki.eclipse.org/Eclipse.ini">https://wiki.eclipse.org/Eclipse.ini</a>.
</p>
<p>
If problems persists after downloading an installation of Eclipse from eclipse.org and using a supported Java runtime environment (a list of which may be found <a
@@ -633,7 +633,7 @@
<a
class="mozTocH4"
name="mozTocId828477"> The default Welcome implementation is HTML-based and requires a supported browser in order to work. If no supported browser can be found, Welcome falls back to its
- Forms-based implementation, which has a different (simpler) appearance. Consult the </a><a href="http://www.eclipse.org/swt/faq.php#browserplatforms">SWT FAQ</a> for supported browsers and setting
+ Forms-based implementation, which has a different (simpler) appearance. Consult the </a><a href="https://www.eclipse.org/swt/faq.php#browserplatforms">SWT FAQ</a> for supported browsers and setting
up your browser to work with eclipse.
</p>
<h4>
@@ -811,7 +811,7 @@
<a
class="mozTocH4"
name="mozTocId69222"> The SWT Browser widget uses a platform-specific web browser to render HTML. The org.eclipse.swt.SWTError exception ("No more handles") is thrown on platforms that don't
- meet the requirements for running the Browser widget. Supported platforms and prerequisites are listed on the SWT FAQ item </a><a href="http://www.eclipse.org/swt/faq.php#browserplatforms">
+ meet the requirements for running the Browser widget. Supported platforms and prerequisites are listed on the SWT FAQ item </a><a href="https://www.eclipse.org/swt/faq.php#browserplatforms">
"Which platforms support the SWT Browser?"</a>.
</p>
<h4>
@@ -1476,7 +1476,7 @@
class="mozTocH3"
name="mozTocId221199"> The startup speed of a shared install can be improved if proper cache information is stored in the shared install area. To achieve this, after unzipping Eclipse
distribution, run Eclipse once with the "-initialize" option from an account that has a write access to the install directory. See </a><a
- href="%20http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fmulti_user_installs.html">shared installs</a> in Eclipse Help for more information.
+ href="%20https://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fmulti_user_installs.html">shared installs</a> in Eclipse Help for more information.
</p>
<h2 id="Upgrading">
<a
@@ -1668,7 +1668,7 @@
<a
class="mozTocH2"
name="mozTocId317294"> See the table in the </a><a
- href="https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_21.xml#appendix">Eclipse 4.21 Project Plan Appendix</a> for
+ href="https://www.eclipse.org/projects/project-plan.php?planurl=https://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_21.xml#appendix">Eclipse 4.21 Project Plan Appendix</a> for
the list of the minimum execution environment (Java class library) requirements of each bundle.
</p>
<hr />
