diff options
| author | Wim Jongman | 2019-02-05 13:36:56 +0000 |
|---|---|---|
| committer | Wim Jongman | 2019-02-05 20:11:11 +0000 |
| commit | 5e461b865c30beb69cda9b8234223800e7943ef8 (patch) | |
| tree | 4e4889989319bd39de193880b8a9aaf4ef8a95b8 | |
| parent | c3ceeadede40affe8325e0bfa1be6ed78bcc89ba (diff) | |
| download | eclipse.platform.common-5e461b865c30beb69cda9b8234223800e7943ef8.tar.gz eclipse.platform.common-5e461b865c30beb69cda9b8234223800e7943ef8.tar.xz eclipse.platform.common-5e461b865c30beb69cda9b8234223800e7943ef8.zip | |
Bug 50517 - Can Error Log view be moved from PDEY20190206-2200I20190206-1800I20190205-1800
Included Error log view in documentation
Change-Id: I5d3895e1c66e2e4d798e29c04320ac83263c9e28
Signed-off-by: Wim Jongman <wim.jongman@remainsoftware.com>
5 files changed, 151 insertions, 0 deletions
diff --git a/bundles/org.eclipse.platform.doc.isv/porting/4.11/faq.html b/bundles/org.eclipse.platform.doc.isv/porting/4.11/faq.html new file mode 100644 index 000000000..d77bbd5c4 --- /dev/null +++ b/bundles/org.eclipse.platform.doc.isv/porting/4.11/faq.html @@ -0,0 +1,28 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html lang="en"> +<head> +<meta name="copyright" content="Copyright (c) 2018 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 4.11 Plug-in Migration FAQ</title> +</head> + +<body> + +<h1>Eclipse 4.11 Plug-in Migration FAQ</h1> + +<ol> + <li><a href="#errorlog">Error Log view moved from PDE to Platform</a></li> +</ol> + +<hr> + +<!-- ############################################## --> +<h2><a name="errorLog">1. Error Log view moved from PDE to Platform</a></h2> +<p>Bundle <code>org.eclipse.ui.views.log</code>, which contains the Error Log view, +has been moved from PDE feature <code>org.eclipse.pde</code> to Platform feature +<code>org.eclipse.platform</code>.</p> +<!-- ############################################## --> +</body> +</html> diff --git a/bundles/org.eclipse.platform.doc.isv/porting/4.11/incompatibilities.html b/bundles/org.eclipse.platform.doc.isv/porting/4.11/incompatibilities.html new file mode 100644 index 000000000..3f161d4f0 --- /dev/null +++ b/bundles/org.eclipse.platform.doc.isv/porting/4.11/incompatibilities.html @@ -0,0 +1,32 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html lang="en"> +<head> +<meta name="copyright" content="Copyright (c) 2018 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=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.10 and 4.11</title> +</head> + +<body> + +<h1>Incompatibilities between Eclipse 4.10 and 4.11</h1> + +<p> + Eclipse changed in incompatible ways between 4.10 and 4.11 in ways that affect + plug-ins. The following entries describe the areas that changed and provide + instructions for migrating 4.10 plug-ins to 4.11. Note that you only need to look + here if you are experiencing problems running your 4.10 plug-in on 4.11. +</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.11/recommended.html b/bundles/org.eclipse.platform.doc.isv/porting/4.11/recommended.html new file mode 100644 index 000000000..9a46eb03d --- /dev/null +++ b/bundles/org.eclipse.platform.doc.isv/porting/4.11/recommended.html @@ -0,0 +1,50 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html lang="en"> +<head> +<meta name="copyright" content="Copyright (c) 2018 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 4.11 mechanisms and APIs</title> +</head> + +<body> + +<h1>Adopting 4.11 mechanisms and APIs</h1> + +<p> + This section describes changes that are required if you are trying to change + your 4.10 plug-in to adopt the 4.11 mechanisms and APIs. +</p> + +<ol> + <li><a href="#errorLog">PDE feature <code>org.eclipse.pde</code> no longer includes the Error Log view.</a></li> +</ol> + +<hr> + +<!-- ############################################## --> +<h2>1. <a name="errorLog">PDE feature <code>org.eclipse.pde</code> no longer includes the Error Log view</a></h2> +<p><strong>What is affected:</strong> Clients including PDE feature <code>org.eclipse.pde</code> to include the Error Log view. +</p> +<p><strong>Description:</strong> +We migrated the <code>org.eclipse.ui.views.log</code> bundle from PDE feature <code>org.eclipse.pde</code> to Platform +feature <code>org.eclipse.platform</code>. The ID of the Error Log view has not been changed. +</p> +<p><strong>Action required:</strong> +Clients should: +</p> +<ul> +<li>Consider removing <code>org.eclipse.pde</code> feature from products if it was included to get the Error Log view.</li> +</ul> +<ul> +<li>Consider adding plug-in <code>org.eclipse.ui.views.log</code> to a private feature or include feature <code>org.eclipse.platform</code> which now contains the Error Log view.</li> +</ul> +<ul> +<li>Consider removing <code>org.eclipse.ui.views.log</code> from private features if feature <code>org.eclipse.platform</code> is already included.</li> +</ul> + +All those changes are backward-compatible. So you can apply them on a project using 4.10 as target-platform, and this would work on both 4.10 and 4.11. + +</body> +</html> diff --git a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_11_porting_guide.html b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_11_porting_guide.html new file mode 100644 index 000000000..d3e6670e0 --- /dev/null +++ b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_11_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) 2017 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 4.11 Plug-in Migration Guide</title> +</head> + +<body> + +<h1>Eclipse 4.11 Plug-in Migration Guide</h1> +<p>This guide covers migrating Eclipse 4.10 plug-ins to Eclipse 4.11.</p> +<p>One of the goals of Eclipse 4.11 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.10 APIs should continue to work in 4.11 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.10 APIs remains valid for + 4.11, 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.11 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.10 plug-ins to + 4.11.</p> +<ul> + <li><a href="4.11/faq.html">Eclipse 4.11 Plug-in Migration FAQ</a></li> + <li><a href="4.11/incompatibilities.html">Incompatibilities between Eclipse 4.10 and 4.11</a></li> + <li><a href="4.11/recommended.html">Adopting 4.11 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 e1117a07f..6e7648f4a 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.11 from 4.10"> + <topic label="Introduction" href="porting/eclipse_4_11_porting_guide.html"/> + <topic label="FAQ" href="porting/4.11/faq.html" /> + <topic label="Incompatibilities" href="porting/4.11/incompatibilities.html" /> + <topic label="Adopting 4.11 mechanisms and API" href="porting/4.11/recommended.html" /> + </topic> <topic label="Migrating to Eclipse 4.10 from 4.9"> <topic label="Introduction" href="porting/eclipse_4_10_porting_guide.html"/> <topic label="FAQ" href="porting/4.10/faq.html" /> |