Bug 553335: Create JDT and Platform porting guides for 4.14 and update
links in Welcome page
Change-Id: Ic972c4d2bd8ce79649dbc1891f172f2ff94ad0f1
Signed-off-by: Kalyan Prasad Tatavarthi <kalyan_prasad@in.ibm.com>
diff --git a/development/porting/eclipse_4_14_porting_guide.html b/development/porting/eclipse_4_14_porting_guide.html
new file mode 100644
index 0000000..9c87004
--- /dev/null
+++ b/development/porting/eclipse_4_14_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 2019. 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 2019-12 (4.14) Plug-in Migration Guide</title>
+</head>
+
+<body>
+
+<h1>Eclipse 2019-12 (4.14) Plug-in Migration Guide</h1>
+<p>This guide covers migrating Eclipse 4.13 plug-ins to Eclipse 4.14.</p>
+<p>One of the goals of Eclipse 4.14 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.13 APIs should continue to work in 4.14 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.13 APIs remains valid for
+ 4.14, 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.14 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.13 plug-ins to
+ 4.14.</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_14_porting_guide.html">
+ Eclipse Platform 2019-12 (4.14) 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">
+ 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_14_porting_guide.html">
+ Eclipse JDT 2019-12 (4.14) Plug-in Migration Guide</a></li>
+</ul>
+
+</body>
+</html>
diff --git a/development/porting/eclipse_4_14_porting_guide.php b/development/porting/eclipse_4_14_porting_guide.php
new file mode 100644
index 0000000..772db32
--- /dev/null
+++ b/development/porting/eclipse_4_14_porting_guide.php
@@ -0,0 +1,12 @@
+<?php
+require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");
+require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php");
+require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php");
+$App = new App();
+$Nav = new Nav();
+$Menu = new Menu();
+/* un-comment to use 100% of the content box
+$right_nav = FALSE;
+*/
+$keyword = 'Eclipse 4.14, API contract compatibility, migrating 4.13 plug-ins to 4.14';
+require_once($_SERVER['DOCUMENT_ROOT'] ."/eclipse/development/nova/_projectCommon.php");
\ No newline at end of file
