Bug 491185 - Change default in project explorer to hierarchical mode
Change-Id: I4d3885efdc1bb3a769da042e16454aa14e260d25
Signed-off-by: Mickael Istria <mistria@redhat.com>
diff --git a/bundles/org.eclipse.platform.doc.isv/porting/4.15/faq.html b/bundles/org.eclipse.platform.doc.isv/porting/4.15/faq.html
new file mode 100644
index 0000000..e94d7fa
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/porting/4.15/faq.html
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html lang="en">
+<head>
+<meta name="copyright" content="Copyright (c) 2020 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.15 Plug-in Migration FAQ</title>
+</head>
+<body>
+<h1>Eclipse 4.15 Plug-in Migration FAQ</h1>
+
+<ol>
+ <li><a href="#project-layout">How can I force a Flat project layout in the <i>Project Explorer</i> view?</a></li>
+</ol>
+
+<hr>
+
+<!-- ############################################## -->
+<h2><a name="project-layout">1. How can I force a Flat project layout in the <i>Project Explorer</i> view?</a></h2>
+<p>As default Project Layout in Project Explorer has been switched to hierarchical, a new preference is available for RCP providers who want to force Flat layout by default instead. The preference is
+<code>org.eclipse.ui.navigator.resources/defaultToFlatLayout</code> and can be set to <code>true</code> in <code>plugin_customization.ini</code> or programatically <i>before</i> Project Explorer opens
+for the first time, in order to force a Flat project layout. Subsequent change to this preference after first initialization of Project Explorer will have no effect.</p>
+<!-- ############################################## -->
+
+</body>
+</html>
diff --git a/bundles/org.eclipse.platform.doc.isv/porting/4.15/incompatibilities.html b/bundles/org.eclipse.platform.doc.isv/porting/4.15/incompatibilities.html
new file mode 100644
index 0000000..5f4d306
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/porting/4.15/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) 2020 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.14 and 4.15</title>
+</head>
+<body>
+<h1>Incompatibilities between Eclipse 4.14 and 4.15</h1>
+
+<p>
+ Eclipse changed in incompatible ways between 4.14 and 4.15 in ways that affect
+ plug-ins. The following entries describe the areas that changed and provide
+ instructions for migrating 4.14 plug-ins to 4.15. Note that you only need to look
+ here if you are experiencing problems running your 4.14 plug-in on 4.15.
+</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.15/recommended.html b/bundles/org.eclipse.platform.doc.isv/porting/4.15/recommended.html
new file mode 100644
index 0000000..5313be2
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/porting/4.15/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) 2020 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.15 mechanisms and APIs</title>
+</head>
+<body>
+<h1>Adopting 4.15 mechanisms and APIs</h1>
+
+<p>
+ This section describes changes that are required if you are trying to change
+ your 4.14 plug-in to adopt the 4.15 mechanisms and APIs.
+</p>
+
+<ol>
+ <li>None</li>
+</ol>
+</body>
+</html>
diff --git a/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_15_porting_guide.html b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_15_porting_guide.html
new file mode 100644
index 0000000..dc83915
--- /dev/null
+++ b/bundles/org.eclipse.platform.doc.isv/porting/eclipse_4_15_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) 2020 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.15 Plug-in Migration Guide</title>
+</head>
+
+<body>
+
+<h1>Eclipse 4.15 Plug-in Migration Guide</h1>
+<p>This guide covers migrating Eclipse 4.14 plug-ins to Eclipse 4.15.</p>
+<p>One of the goals of Eclipse 4.15 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.14 APIs should continue to work in 4.15 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.14 APIs remains valid for
+ 4.15, 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.15 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.14 plug-ins to
+ 4.15.</p>
+<ul>
+ <li><a href="4.15/faq.html">Eclipse 4.15 Plug-in Migration FAQ</a></li>
+ <li><a href="4.15/incompatibilities.html">Incompatibilities between Eclipse 4.14 and 4.15</a></li>
+ <li><a href="4.15/recommended.html">Adopting 4.14 mechanisms and API</a></li>
+</ul>
+
+</body>
+</html>
