diff options
| author | Kalyan Prasad Tatavarthi | 2019-08-28 09:25:30 +0000 |
|---|---|---|
| committer | Kalyan Prasad Tatavarthi | 2019-08-28 09:27:23 +0000 |
| commit | c4621aaadbb2da0ace6300fccccff900561cb19c (patch) | |
| tree | 50d1b7143a835c80c31f7b7fcb1fed665145fbf8 | |
| parent | 67901d927a87c0315fb8d98ddb844977c5efa8d7 (diff) | |
| download | eclipse.platform.common-c4621aaadbb2da0ace6300fccccff900561cb19c.tar.gz eclipse.platform.common-c4621aaadbb2da0ace6300fccccff900561cb19c.tar.xz eclipse.platform.common-c4621aaadbb2da0ace6300fccccff900561cb19c.zip | |
Bug 550516 - Create JDT and Platform porting guides for 4.13 and update
links in Welcome page
Change-Id: I16d171f9d5e4a4bce5cd50a98512422b6d17c9d3
Signed-off-by: Kalyan Prasad Tatavarthi <kalyan_prasad@in.ibm.com>
10 files changed, 217 insertions, 0 deletions
diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/4.13/faq.html b/bundles/org.eclipse.jdt.doc.isv/porting/4.13/faq.html new file mode 100644 index 000000000..4b1d6428a --- /dev/null +++ b/bundles/org.eclipse.jdt.doc.isv/porting/4.13/faq.html @@ -0,0 +1,20 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html lang="en"> +<head> +<meta name="copyright" content="Copyright (c) 2019 IBM Corporation and others. 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 JDT 4.13 Plug-in Migration FAQ</title> +</head> + +<body> + +<h1>Eclipse JDT 4.13 Plug-in Migration FAQ</h1> + +<ol> + <li>None</li> +</ol> + +</body> +</html> diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/4.13/incompatibilities.html b/bundles/org.eclipse.jdt.doc.isv/porting/4.13/incompatibilities.html new file mode 100644 index 000000000..370020cb4 --- /dev/null +++ b/bundles/org.eclipse.jdt.doc.isv/porting/4.13/incompatibilities.html @@ -0,0 +1,19 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html lang="en"> +<head> +<meta name="copyright" content="Copyright (c) 2019 IBM Corporation and others. 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>Incompatibilities between Eclipse JDT 4.12 and 4.13</title> +</head> +<body> +<h1>Incompatibilities between Eclipse JDT 4.12 and 4.13</h1> + +<p> + So far Eclipse did not change incompatibly between 4.12 and 4.13 in ways that affect + plug-ins. Plug-ins that ran on 4.12 should run on 4.13 without any problems. +</p> + +</body> +</html> diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/4.13/recommended.html b/bundles/org.eclipse.jdt.doc.isv/porting/4.13/recommended.html new file mode 100644 index 000000000..769c08012 --- /dev/null +++ b/bundles/org.eclipse.jdt.doc.isv/porting/4.13/recommended.html @@ -0,0 +1,23 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html lang="en"> +<head> +<meta name="copyright" content="Copyright (c) 2019 IBM Corporation and others. 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>Adopting JDT 4.13 mechanisms and APIs</title> +</head> + +<body> + +<h1>Adopting JDT 4.13 mechanisms and APIs</h1> +<p> + This section describes changes that are required if you are trying to change + your 4.12 plug-in to adopt the 4.13 mechanisms and APIs. +</p> + +<ol> + <li>None</li> +</ol> +</body> +</html> diff --git a/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_4_13_porting_guide.html b/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_4_13_porting_guide.html new file mode 100644 index 000000000..cc8acee71 --- /dev/null +++ b/bundles/org.eclipse.jdt.doc.isv/porting/eclipse_4_13_porting_guide.html @@ -0,0 +1,39 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html lang="en"> + +<head> + +<meta name="copyright" content="Copyright (c) IBM 2019 Corporation and others. 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 JDT 4.13 Plug-in Migration Guide</title> +</head> + +<body> + +<h1>Eclipse JDT 4.13 Plug-in Migration Guide</h1> +<p>This guide covers migrating Eclipse JDT 4.12 plug-ins to Eclipse JDT 4.13.</p> +<p>One of the goals of Eclipse 4.13 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.12 APIs should continue to work in 4.13 in spite of the + 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.12 APIs remains valid for + 4.13, 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.13 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. + This document describes those areas and provides instructions for migrating 4.12 plug-ins to + 4.13.</p> +<ul> + <li><a href="4.13/faq.html">Eclipse JDT 4.13 Plug-in Migration FAQ</a></li> + <li><a href="4.13/incompatibilities.html">Incompatibilities between Eclipse JDT 4.12 and 4.13</a></li> + <li><a href="4.13/recommended.html">Adopting 4.13 mechanisms and API</a></li> +</ul> + +</body> +</html>
\ No newline at end of file diff --git a/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml b/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml index d50efe6aa..56c7c79d4 100644 --- a/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml +++ b/bundles/org.eclipse.jdt.doc.isv/topics_Porting.xml @@ -4,6 +4,12 @@ <!-- Define topics for the porting guide index --> <!-- ============================================================================= --> <toc label="Migration"> + <topic label="Migrating to Eclipse JDT 4.13 from 4.12"> + <topic label="Introduction" href="porting/eclipse_4_13_porting_guide.html"/> + <topic label="FAQ" href="porting/4.13/faq.html" /> + <topic label="Incompatibilities" href="porting/4.13/incompatibilities.html" /> + <topic label="Adopting 4.13 Mechanisms and API" href="porting/4.13/recommended.html" /> + </topic> <topic label="Migrating to Eclipse JDT 4.12 from 4.11"> <topic label="Introduction" href="porting/eclipse_4_12_porting_guide.html"/> <topic label="FAQ" href="porting/4.12/faq.html" /> diff --git a/bundles/org.eclipse.platform.doc.isv/porting/4.13/faq.html b/bundles/org.eclipse.platform.doc.isv/porting/4.13/faq.html new file mode 100644 index 000000000..2742edd2f --- /dev/null +++ b/bundles/org.eclipse.platform.doc.isv/porting/4.13/faq.html @@ -0,0 +1,18 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html lang="en"> +<head> +<meta name="copyright" content="Copyright (c) 2019 Red Hat Inc. and others. 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 4.13 Plug-in Migration FAQ</title> +</head> +<body> +<h1>Eclipse 4.13 Plug-in Migration FAQ</h1> + +<ol> + <li>None</li> +</ol> + +</body> +</html> diff --git a/bundles/org.eclipse.platform.doc.isv/porting/4.13/incompatibilities.html b/bundles/org.eclipse.platform.doc.isv/porting/4.13/incompatibilities.html new file mode 100644 index 000000000..c23c5de4c --- /dev/null +++ b/bundles/org.eclipse.platform.doc.isv/porting/4.13/incompatibilities.html @@ -0,0 +1,29 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html lang="en"> +<head> +<meta name="copyright" content="Copyright (c) 2019 Red Hat Inc. and others. 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=UTF-8"> +<meta http-equiv="Content-Style-Type" content="text/css"> +<link rel="STYLESHEET" href="../../book.css" charset="ISO-8859-1" type="text/css"> +<title>Incompatibilities between Eclipse 4.12 and 4.13</title> +</head> +<body> +<h1>Incompatibilities between Eclipse 4.12 and 4.13</h1> + +<p> + Eclipse changed in incompatible ways between 4.12 and 4.13 in ways that affect + plug-ins. The following entries describe the areas that changed and provide + instructions for migrating 4.12 plug-ins to 4.13. Note that you only need to look + here if you are experiencing problems running your 4.12 plug-in on 4.13. +</p> +<p> +See also the list of <a href="../removals.html">deprecated API removals</a> for this release. +</p> + + +<hr> + +<!-- ############################################## --> + +</body> +</html> diff --git a/bundles/org.eclipse.platform.doc.isv/porting/4.13/recommended.html b/bundles/org.eclipse.platform.doc.isv/porting/4.13/recommended.html new file mode 100644 index 000000000..b3e5ccf42 --- /dev/null +++ b/bundles/org.eclipse.platform.doc.isv/porting/4.13/recommended.html @@ -0,0 +1,22 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html lang="en"> +<head> +<meta name="copyright" content="Copyright (c) 2019 Red Hat Inc. and others. 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>Adopting 4.12 mechanisms and APIs</title> +</head> +<body> +<h1>Adopting 4.13 mechanisms and APIs</h1> + +<p> + This section describes changes that are required if you are trying to change + your 4.12 plug-in to adopt the 4.13 mechanisms and APIs. +</p> + +<ol> + <li>None</li> +</ol> +</body> +</html> diff --git a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_13_porting_guide.html b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_13_porting_guide.html new file mode 100644 index 000000000..d58dfef51 --- /dev/null +++ b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_13_porting_guide.html @@ -0,0 +1,35 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html lang="en"> +<head> +<meta name="copyright" content="Copyright (c) 2019 Red Hat Inc. and others. 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 4.13 Plug-in Migration Guide</title> +</head> + +<body> + +<h1>Eclipse 4.13 Plug-in Migration Guide</h1> +<p>This guide covers migrating Eclipse 4.12 plug-ins to Eclipse 4.13.</p> +<p>One of the goals of Eclipse 4.13 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.12 APIs should continue to work in 4.13 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.12 APIs remains valid for + 4.13, 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.13 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. + This document describes those areas and provides instructions for migrating 4.12 plug-ins to + 4.13.</p> +<ul> + <li><a href="4.13/faq.html">Eclipse 4.13 Plug-in Migration FAQ</a></li> + <li><a href="4.13/incompatibilities.html">Incompatibilities between Eclipse 4.12 and 4.13</a></li> + <li><a href="4.13/recommended.html">Adopting 4.13 mechanisms and API</a></li> +</ul> + +</body> +</html> diff --git a/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml b/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml index 0a2f4e48a..5005b92d9 100644 --- a/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml +++ b/bundles/org.eclipse.platform.doc.isv/topics_Porting.xml @@ -5,6 +5,12 @@ <!-- ============================================================================= --> <toc label="Migration"> <topic label="Deprecated API removals" href="porting/removals.html"/> + <topic label="Migrating to Eclipse 4.13 from 4.12"> + <topic label="Introduction" href="porting/eclipse_4_13_porting_guide.html"/> + <topic label="FAQ" href="porting/4.13/faq.html" /> + <topic label="Incompatibilities" href="porting/4.13/incompatibilities.html" /> + <topic label="Adopting 4.13 mechanisms and API" href="porting/4.13/recommended.html" /> + </topic> <topic label="Migrating to Eclipse 4.12 from 4.11"> <topic label="Introduction" href="porting/eclipse_4_12_porting_guide.html"/> <topic label="FAQ" href="porting/4.12/faq.html" /> |