Bug 437930: Deploy New and Noteworthy on www.eclipse.org/eclipse
diff --git a/platform/4.2/M1/default_style.css b/platform/4.2/M1/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.2/M1/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.2/M1/eclipse-news-M1.html b/platform/4.2/M1/eclipse-news-M1.html
deleted file mode 100644
index cdd78c2..0000000
--- a/platform/4.2/M1/eclipse-news-M1.html
+++ /dev/null
@@ -1,71 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2011."/>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Juno M1 New and Noteworthy</title>
-</head>
-<body>
-<h1>Eclipse Juno M1 New and Noteworthy</h1>
-<p>Here are the noteworthy things available in milestone build M1 
-  (August 5, 2011) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
- </p>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-
-    <td colspan="2" class="section" id="Platform">Equinox and Platform</td>
-  </tr>
-
-  <tr id="git-migration">
-    <td class="title">Git migration</td>
-    <td class="content">
-	During M1 the Equinox and Platform teams were busy with the Git migration. So far the following got migrated:
-	<ul>
-		<li>Equinox</li>
-		<li>SWT</li>
-		<li>Platform Runtime</li>
-		<li>Platform UI</li>
-	</ul>
-    </td>
-  </tr>
-
-
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  
-  <tr id="jdt-java7">
-    <td class="title">Java 7 support</td>
-
-    <td class="content">
-        Promptly after Java 7 has been officially released, Eclipse also fully supports it.
-        See <a href="http://www.eclipse.org/jdt/ui/r3_8/Java7news/whats-new-java-7.html">What's new for Java 7</a> for the new Java 7 related features offered by JDT.
-    </td>
-  </tr>
-   
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  
-      
-  <tr id="vendor-history">
-    <td class="title">Plug-in vendor history</td>
-    <td class="content">
-      When creating a new plug-in, fragment or feature the Vendor information used in the creation wizard is retained and can be reused
-      by selecting the drop-down in subsequent uses of the wizard.
-      <p>
-        <img src="images/pde-wizard.png" alt="The Vendor history drop-down"/>
-      </p>
-    </td>
-  </tr>
-
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-
-</table>
-</body>
-</html>
diff --git a/platform/4.2/M1/eclipse-news-M1.zip b/platform/4.2/M1/eclipse-news-M1.zip
deleted file mode 100644
index d872f04..0000000
--- a/platform/4.2/M1/eclipse-news-M1.zip
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M1/images/pde-wizard.png b/platform/4.2/M1/images/pde-wizard.png
deleted file mode 100644
index bee9018..0000000
--- a/platform/4.2/M1/images/pde-wizard.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M2/4.2M2-news.zip b/platform/4.2/M2/4.2M2-news.zip
deleted file mode 100644
index 8812c00..0000000
--- a/platform/4.2/M2/4.2M2-news.zip
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M2/default_style.css b/platform/4.2/M2/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.2/M2/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.2/M2/eclipse-news-M2.html b/platform/4.2/M2/eclipse-news-M2.html
deleted file mode 100644
index 9eb6d41..0000000
--- a/platform/4.2/M2/eclipse-news-M2.html
+++ /dev/null
@@ -1,129 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Juno M2 News</title>
-</head>
-<body>
-<h1>Eclipse Juno M2 - New and Noteworthy</h1>
-<p>As the <a href="http://www.nasa.gov/mission_pages/juno/overview/index.html">Juno spacecraft</a>
-rockets towards Jupiter, the <a href="http://wiki.eclipse.org/Juno">Juno train</a> is also making
-good progress. Here are some of the more noteworthy things available in milestone build M2 
- (September 16, 2011) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-Unless otherwise indicated, all entries listed here are available in both the 3.8 and 4.2 development streams.
-See the <a href="buildNotes.php">build notes</a> for details about bugs fixed and other changes.</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  
-  <tr id="platform-fade-effects">
-    <td width="30%" valign="top" align="left"><b>Fade Transition on Maximize (4.2 only)</b></td>
-    <td width="70%" valign="top">
-	It's fall and the weather is getting cool...so we should too. For the first step we've 
-	added a 'fade' effect to the maximize / restore operation. Let us know what you think by leaving your comments
-	in <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=357939">bug 357939</a>. If it's 
-	popular we can add similar effects to other transitions in the user interface such as perspective switching.
-	<p>
-	Note that this is an early implementation, and there are known issues with the implementation on various 
-	platforms that we're working on fixing. You can turn the fade 
-	effect off using the animations preference (found under <b>Window &gt; Preferences &gt; General &gt; Appearance</b>) 
-	should you prefer to return to the old effect.
-	</p>
-	<iframe width="420" height="315" src="http://www.youtube.com/embed/07kESXY5m2Q" frameborder="0" allowfullscreen></iframe>    
-	</td>
-  </tr>
-
-  <tr id="ant-editor-extension-point">
-    <td class="title">Enhanced Editor Support for Ant 1.8.2</td>
-    <td class="content">
-      The Ant editor has been enhanced with support for the new <a href="http://ant.apache.org/manual/targets.html#extension-points">extension-point</a> 
-      features in Ant 1.8.2.
-      <p><img src="images/ant-extension-assist.png" alt="Ant extension point editor content assist"/></p>
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr id="jdt-convert-enhanced-for-loop">
-    <td class="title">Quick Assist to convert enhanced <code>for</code> loop</td>
-    <td class="content">
-      Ever encountered an enhanced <code>for</code> loop and needed access to the <code>Iterator</code> or to the loop index?
-      Now, you can just use a Quick Assist (<b>Ctrl+1</b>) to convert the loop:
-      <p>
-          <img src="images/convert-to-for-loop.png" alt="Screenshot of Quick Assist on the 'for' keyword of an enhanced 'for' loop"/>
-      </p>
-      
-      <ul>
-        <li><b>Convert to indexed 'for' loop</b> is available for expressions of array- and <code>List</code>-based types.</li>
-        <li><b>Convert to Iterator-based 'for' loop</b> is available for expressions of type <code>Iterable</code>.</li>
-      </ul>
-    </td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-
-  <tr id="pde-git-migration">
-    <td class="title">PDE migrated to Git repository</td>
-    <td class="content">
-	All PDE code has been migrated from CVS to a Git repository.
-
-	<p>PDE UI and API Tools code can be accessed at <a href="http://git.eclipse.org/c/pde/eclipse.pde.ui.git/">git://git.eclipse.org/gitroot/pde/eclipse.pde.ui.git</a></p>
-
-	<p>PDE Build code can be accessed at <a href="http://git.eclipse.org/c/pde/eclipse.pde.build.git/">git://git.eclipse.org/gitroot/pde/eclipse.pde.build.git</a></p>
-
-	<p>PDE Incubator code can be accessed at <a href="http://git.eclipse.org/c/pde/eclipse.pde.incubator.git/">git://git.eclipse.org/gitroot/pde/eclipse.pde.incubator.git</a></p>
-	</td>
-  </tr>
-
-
-  <tr id="pde-classpath-api">
-    <td class="title">Bundle classpath resolution API</td>
-    <td class="content">
-	The <b>org.eclipse.pde.core.bundleClasspathResolvers</b> extension point allows 
-	you to dynamically add additional content to the runtime classpath and source 
-	lookup path of workspace plug-ins at launch time.
-	</td>
-  </tr>
-  
-
-  <tr id="pde-import-package-explorer">
-    <td class="title">Import from repository in the Package Explorer view</td>
-    <td class="content">
-		 By using <b>File &gt; Import... &gt; Import Plug-ins and Fragments</b> you can import the source
-		 code for a plug-in from your installation if the plug-in has the necessary manifest header.
-		 Now you can access this functionality directly from the Package Explorer and Project Explorer
-		 views.  Right click on a plug-in in your project's <b>Plug-in Dependencies</b> classpath container
-		 and select <b>Import from Repository...</b>.
-
-		 <p><img src="images/import-repo-pkg.png" alt="Import from repository in package explorer view"/></p>
-
-		 <p>Importing from a repository is also available in the Target Platform State, Plug-in Dependencies and Plug-ins 
-		 views.  If the selected item can be imported, there will be an <b>Import As</b> menu visible when right clicking in
-		 the view.</p>
-
-		 <p><img src="images/import-repo-tps.png" alt="Import from repository in target platform state view"/></p>
-	</td>
-  </tr>
-  
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Juno milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops/S-3.8M1-201108031800/eclipse-news-M1.html">New for Eclipse Juno milestone build M1 (August 5, 2011)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.2/M2/images/ant-extension-assist.png b/platform/4.2/M2/images/ant-extension-assist.png
deleted file mode 100644
index 1246bf0..0000000
--- a/platform/4.2/M2/images/ant-extension-assist.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M2/images/convert-to-for-loop.png b/platform/4.2/M2/images/convert-to-for-loop.png
deleted file mode 100644
index ef74a8e..0000000
--- a/platform/4.2/M2/images/convert-to-for-loop.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M2/images/import-repo-pkg.png b/platform/4.2/M2/images/import-repo-pkg.png
deleted file mode 100644
index 244e47f..0000000
--- a/platform/4.2/M2/images/import-repo-pkg.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M2/images/import-repo-tps.png b/platform/4.2/M2/images/import-repo-tps.png
deleted file mode 100644
index 05d34b0..0000000
--- a/platform/4.2/M2/images/import-repo-tps.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/4.2M3-news.zip b/platform/4.2/M3/4.2M3-news.zip
deleted file mode 100644
index c88cf1c..0000000
--- a/platform/4.2/M3/4.2M3-news.zip
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/default_style.css b/platform/4.2/M3/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.2/M3/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.2/M3/eclipse-news-M3.html b/platform/4.2/M3/eclipse-news-M3.html
deleted file mode 100644
index 0ff9676..0000000
--- a/platform/4.2/M3/eclipse-news-M3.html
+++ /dev/null
@@ -1,277 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse 3.8 and 4.2 M3 News</title>
-</head>
-<body>
-<h1>Eclipse 3.8 and 4.2 M3 - New and Noteworthy</h1>
-<p><a href="http://en.wikipedia.org/wiki/File:Denarius-Julia_Soaemias-RIC_0237.jpg">Queen Juno</a>
-was a patron goddess of ancient Rome, and now assumes a tutelar role for the Eclipse Foundation's next
-<a href="http://wiki.eclipse.org/Simultaneous_Release">simultaneous release</a>. Here are some of 
-the more noteworthy things available in milestone build M3 
-  (October 28, 2011) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-Unless otherwise indicated, all entries listed here are available in both the 3.8 and 4.2 development streams.
-See the <a href="buildNotes.php">build notes</a> for details about bugs fixed and other changes.</p>
-<ul>
-  <li><a href="#Equinox">Equinox</a></li>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Equinox">Equinox</td>
-  </tr>
-  <tr id="Equinox-console">
-    <td class="title">New OSGi console</td>
-    <td class="content">
-      This milestone includes a brand new OSGi console based on the Apache Felix Gogo project.
-	  In previous releases the Equinox framework contained a built-in OSGi console. 
-	  This console allows you to interact with the OSGi framework and execute commands 
-	  on the running instance of the framework. For example, it can be used to install bundles 
-	  or to get a list of currently installed bundles. The built-in console is convenient because 
-	  it is always available without needing to install extra bundles, but it is also limited
-	  because the framework itself must contain all the functionality of the built-in console. 
-	  <p>
-      The Apache Felix Gogo project has developed an advanced shell for interacting with OSGi frameworks. 
-      Instead of continually enhancing the built-in Equinox Framework console, a new external Equinox 
-      Console bundle has been created that uses the Apache Felix Gogo bundles. The new Equinox Console 
-      bundle continues to provide support for the Equinox Console APIs (package 
-      <tt>org.eclipse.osgi.framework.console</tt>). It also adds many new enhancements which are 
-      possible through the use of the Gogo shell. This includes features such as tab completion, 
-      command history, piping, grep, telnet and ssh connections, and more. Type <i>help</i> on the console 
-      to see a list of available commands, or <i>help &lt;command-name&gt;</i> for information on 
-      how to use each command.
-      </p>
-    </td>
-  </tr>
-  <tr>
-    <td id="Platform" class="section" colspan="2">
-      <h2>Platform</h2>
-    </td>
-  </tr>
-
-  <tr id="Platform-debug-toolbar">
-    <td class="title">Global debug toolbar</td>
-    <td class="content">To improve the presentation of the debug perspective, you can now move the 
-    toolbar out of the <b>Debug</b> view and into the global toolbar - or use it in the view and in the toolbar.
-	<p><img src="images/debug_toolbar-1.png" alt="Global debug toolbar"/></p>
-    <p>
-	The global toolbar contains the same commands as the view toolbar, but can be customized with  
-	<b>Window &gt; Customize Perspective...</b> to add or remove debugging commands, or the entire 
-	debug toolbar. The visibility of the debug toolbar can be changed using 
-	<b>Show Debug Toolbar</b> in the <b>Debug</b> view's menu.</p>
-	<p><img src="images/debug_toolbar-2.png" alt="Debug view toolbar action" /></p>
-    </td>
-  </tr>
-
-  <tr id="Platform-use-saturated-colors">
-    <td class="title">Use saturated colors in overview ruler</td>
-    <td class="content">
-      The new <b>Use saturated colors in overview ruler</b> preference allows to show the annotations in the Overview ruler using saturated colors:
-      <p>
-          <img src="images/use-saturated-colors-on.png" alt="Screenshot with saturated colors" title="saturated colors"/>
-          &nbsp;
-          <img src="images/use-saturated-colors-off.png" alt="Screenshot without saturated colors" title="lighter colors"/>
-          &nbsp;
-          <img src="images/use-saturated-colors.png" alt="Screenshot of the 'Accessibility' preference page"/>
-      </p>
-      <p>
-        This option is turned off by default and can be enabled on the <b>General &gt; Editors &gt; Text Editors &gt; Accessibility</b>
-        page.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="Platform-delete-project">
-    <td class="title">Delete project dialog shows project location</td>
-    <td class="content">
-      The Delete Resources dialog now shows the location of deleted projects on the file system:
-      <p>
-          <img src="images/delete-project.png" alt="Screenshot"/>
-      </p>
-    </td>
-  </tr>
-
-	<tr id="SWT-cocoa-highlight">
-   	    <td class="title">Highlight TrayItem Image</td>
-   	    <td class="content">You can now provide a custom image for use as the hightlight image for 
-    	    a tray item on Cocoa. The highlight image is shown when the tray item is activated. 
-    	    The default tray item image will be restored when the tray item is deactivated.
-		   <p><i>Default Tray Item</i><br/><img src="images/nohighlight.png" alt="Default Tray Item"/></p>
-		   <p><i>Highlighted Tray Item</i><br/><img src="images/highlight.png" alt="Highlighted Tray Item"/></p>
-  	    </td>
-  	</tr>
-	<tr id="SWT-styledtext-scrollbars">
-   	    <td class="title">Added support in StyledText to show the scrollbars only when needed</td>
-   	    <td class="content">In the past, when a StyledText was created with scrollbars it would show 
-   	    them all the time, even when the client area was big enough to show the entire content.
-		By using <code>setAlwaysShowScrollBars()</code> this behaviour can now be configured so that 
-		instead of showing a disabled scrollbar, the StyledText will only display the scrollbar when needed.
-   	     </td>
-  	</tr>
-	<tr id="SWT-styledtext-events">
-   	    <td class="title">Event type constants in StyledText are now public</td>
-   	    <td class="content">
-   		 The following event type constants in <tt>StyledText</tt> have been made public:
-		<ul>
-		<li>ExtendedModify</li>
-		<li>LineGetBackground</li>
-		<li>LineGetStyle</li>
-		<li>TextChanging</li> 
-		<li>TextSet</li>
-		<li>VerifyKey</li>
-		<li>TextChanged</li>
-		<li>LineGetSegments</li>
-		<li>PaintObject</li>
-		<li>WordNext</li>
-		<li>WordPrevious</li>
-		<li>CaretMoved </li>
-		</ul>
-		This allows these constants to be used with <tt>Widget#isListening()</tt> to verify if a 
-		listener handler was added for any event type in <tt>StyledText</tt>.
-   	     </td>
-  	</tr>
-	<tr id="SWT-default-browser">
-   	    <td class="title">Default Browser renderer is now configurable</td>
-   	    <td class="content">
-   		 The native renderer that is used for <code>SWT.NONE</code>-style browsers can now be 
-   		 configured by setting a Java property. This is particularly important for applications 
-   		 that create browsers with a specific native renderer style (eg.- <code>SWT.MOZILLA</code>), 
-   		 in order to avoid conflicts that can occur when multiple native renderers are loaded in 
-   		 the same process.
-		<p>For more information on using this new property see 
-		<a href="http://www.eclipse.org/swt/faq.php#browserspecifydefault">How do I specify the 
-		default type of native renderer that is used by the Browser?</a> .</p>
-   	     </td>
-  	</tr>
-	<tr id="SWT-fontdialog">
-   	    <td class="title">FontDialog Effects</td>
-   	    <td class="content">
-   		 New API has been added to <tt>FontDialog</tt> to prevent the user from selecting font effects,
-   		 such as color, underline, strikethrough and shadow.
-		 <p><img src="images/font-dialog-effects.png" alt="FontDialog on Windows without the Effects grouping"/></p>
-   	     </td>
-  	</tr>
-	<tr id="SWT-combo-api">
-   	    <td class="title">New Combo API</td>
-   	    <td class="content">
-		Two new APIs have been added to <tt>Combo</tt> that allow users to get the caret information 
-		in a combo box. <code>Combo.getCaretLocation</code> returns the pixel coordinates of the 
-		caret. <code>Combo.getCaretPosition</code> returns the character position of the caret.
- 		<p>
-		For an example of how to use this API see 
-		<a href="http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/examples/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet359.java">Snippet 359</a>.
-		</p>
-   	    </td>
-  	</tr>
-  
-  <tr>
-    <td id="JDT" class="section" colspan="2">
-      <h2>JDT</h2>
-    </td>
-  </tr>
-
-  <tr id="JDT-editor-for-class-without-source">
-    <td class="title">'*.class without source' file type</td>
-    <td class="content">
-      The new <b>*.class without source</b> file type allows to associate an internal or external editor
-      to class files that have no source attached. This e.g. allows to open the class file in a decompiler:
-      <p>
-          <img src="images/file-associations-page.png" alt="Screenshot of the 'File Associations' preference page"/>
-      </p>
-    </td>
-  </tr>
-
-  <tr id="JDT-property-key-quick-assists">
-    <td class="title">Quick assists to reorganize property keys</td>
-    <td class="content">
-      If you use Eclipse-style externalized strings, the following new quick assists make it easier to
-      reorganize keys inside the <b>Properties File Editor</b>:
-      <ul>
-          <li><b>Rename in workspace</b> - renames the key in the properties file and updates all references</li>
-          <li><b>Create field in '...'</b> - creates the corresponding field in the resource bundle accessor class</li>
-          <li><b>Remove property</b> - deletes the property from the properties file and the field from the resource bundle accessor class</li>
-          <li><b>Remove properties</b> - deletes the selected properties from the properties file and the fields from the resource bundle accessor class</li>
-      </ul>
-    </td>
-  </tr>
-
-  <tr id="JDT-resource-leaks">
-    <td class="title">New options to detect resource leaks</td>
-    <td class="content">The compiler can now detect leakage of resources i.e. local variables of type
-      <code>java.lang.AutoCloseable</code> (compliance &gt;= 1.7) and <code>java.io.Closeable</code> (compliance &lt;= 1.6).
-      <p>
-       <img src="images/resource-leak-warnings.png"
-          alt="Configurable options on compiler errors/warnings preference page"
-          title="Configurable options on compiler errors/warnings preference page"/>
-      </p>
-      <p> When the <b>Resource leak</b> option on the <b>Java &gt; Compiler &gt; Errors/Warnings</b> preference page is enabled,
-      the compiler will issue an error or a warning if the <code>close()</code> method is not invoked locally on a resource.</p>
-      <p>
-       <img src="images/resource-leak-example.png"
-          alt="Resource leak example"
-          title="Compiler warning on an unclosed resource"/>
-      </p>
-
-      <p> When you enable the <b>Potential resource leak</b> option on the <b>Java &gt; Compiler &gt; Errors/Warnings</b> preference page,
-      the compiler will issue an error or a warning if the <code>close()</code> method is not invoked locally on a resource
-      on all the execution paths.</p>
-      <p>
-       <img src="images/pot-resource-leak-example.png"
-          alt="Potential resource leak example"
-          title="Compiler warning on a resource not closed on all execution paths"/>
-      </p>
-      </td>
-    </tr>
-
-    <tr id="JDT-try-with-resource">
-    <td class="title">New options to suggest use of <code>try</code>-with-resources statement</td>
-    <td class="content">The compiler can now suggest using try with resources statement
-      for resources of type <code>java.lang.AutoCloseable</code> when
-      such resources have been explicitly closed but not declared in <code>try</code>-with-resources statements.
-      This only works in compliance 1.7 or above.
-       <p>
-       <img src="images/twr-example.png"
-          alt="Compiler warning for a resource that should be managed with try-with-resource"
-          title="Compiler warning for a resource that should be managed with try-with-resource"/></p>
-      </td></tr>
-
-      <tr id="JDT-batch-compiler">
-    <td class="title">New Batch compiler warning options</td>
-
-    <td class="content">Two new batch compiler options are now available to configure the
-      compile time warnings:
-      <ul>
-      	<li><b>-warn:all</b> can be used to enable all compiler warnings</li>
-      	<li><b>-warn:resource</b> can be used to enable resource leak warnings</li>
-      </ul>
-      </td></tr>
-      <tr id="JDT-build-path">
-    <td class="title">New build path option to warn when a source folder's output location overlaps another source folder</td>
-
-    <td class="content">JDT now shows a build path error when a source folder's output location overlaps another source folder.
-       This error can be configured on the <b>Java &gt; Compiler &gt; Building &gt; Output location overlaps source location</b> preference page.
-       <p>
-       <img src="images/buildpath-error.png"
-          alt="Build path error when source folder's output location overlaps another source folder"
-          title="Build path error because src2's output location is src"/></p>
-    </td>
-  </tr>
-      
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Juno milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M2-201109161615/eclipse-news-M2.html">New for Eclipse Juno milestone build M2 (September 16, 2010)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops/S-3.8M1-201108031800/eclipse-news-M1.html">New for Eclipse Juno milestone build M1 (August 5, 2011)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.2/M3/images/buildpath-error.png b/platform/4.2/M3/images/buildpath-error.png
deleted file mode 100644
index f7e4be8..0000000
--- a/platform/4.2/M3/images/buildpath-error.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/debug_toolbar-1.png b/platform/4.2/M3/images/debug_toolbar-1.png
deleted file mode 100644
index 737a495..0000000
--- a/platform/4.2/M3/images/debug_toolbar-1.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/debug_toolbar-2.png b/platform/4.2/M3/images/debug_toolbar-2.png
deleted file mode 100644
index e1d4f02..0000000
--- a/platform/4.2/M3/images/debug_toolbar-2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/delete-project.png b/platform/4.2/M3/images/delete-project.png
deleted file mode 100644
index 700ca95..0000000
--- a/platform/4.2/M3/images/delete-project.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/file-associations-page.png b/platform/4.2/M3/images/file-associations-page.png
deleted file mode 100644
index 6c8994f..0000000
--- a/platform/4.2/M3/images/file-associations-page.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/font-dialog-effects.png b/platform/4.2/M3/images/font-dialog-effects.png
deleted file mode 100644
index c83732c..0000000
--- a/platform/4.2/M3/images/font-dialog-effects.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/highlight.png b/platform/4.2/M3/images/highlight.png
deleted file mode 100644
index daf180c..0000000
--- a/platform/4.2/M3/images/highlight.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/nohighlight.png b/platform/4.2/M3/images/nohighlight.png
deleted file mode 100644
index a57a7c2..0000000
--- a/platform/4.2/M3/images/nohighlight.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/pot-resource-leak-example.png b/platform/4.2/M3/images/pot-resource-leak-example.png
deleted file mode 100644
index 09d699c..0000000
--- a/platform/4.2/M3/images/pot-resource-leak-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/resource-leak-example.png b/platform/4.2/M3/images/resource-leak-example.png
deleted file mode 100644
index d1b400e..0000000
--- a/platform/4.2/M3/images/resource-leak-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/resource-leak-warnings.png b/platform/4.2/M3/images/resource-leak-warnings.png
deleted file mode 100644
index 18110b7..0000000
--- a/platform/4.2/M3/images/resource-leak-warnings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/twr-example.png b/platform/4.2/M3/images/twr-example.png
deleted file mode 100644
index 540f8be..0000000
--- a/platform/4.2/M3/images/twr-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/use-saturated-colors-off.png b/platform/4.2/M3/images/use-saturated-colors-off.png
deleted file mode 100644
index bc09783..0000000
--- a/platform/4.2/M3/images/use-saturated-colors-off.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/use-saturated-colors-on.png b/platform/4.2/M3/images/use-saturated-colors-on.png
deleted file mode 100644
index 23dbdd9..0000000
--- a/platform/4.2/M3/images/use-saturated-colors-on.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M3/images/use-saturated-colors.png b/platform/4.2/M3/images/use-saturated-colors.png
deleted file mode 100644
index e4af0bc..0000000
--- a/platform/4.2/M3/images/use-saturated-colors.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M4/4.2M4-news.zip b/platform/4.2/M4/4.2M4-news.zip
deleted file mode 100644
index a58e8b4..0000000
--- a/platform/4.2/M4/4.2M4-news.zip
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M4/default_style.css b/platform/4.2/M4/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.2/M4/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.2/M4/eclipse-news-M4.html b/platform/4.2/M4/eclipse-news-M4.html
deleted file mode 100644
index 37540e0..0000000
--- a/platform/4.2/M4/eclipse-news-M4.html
+++ /dev/null
@@ -1,277 +0,0 @@
-<!DOCTYPE html>
-<html>
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse 3.8 and 4.2 M4 News</title>
-</head>
-<body>
-<h1>Eclipse 3.8 and 4.2 M4 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M4 
-  (December 9, 2011) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-Unless otherwise indicated, all entries listed here are available in both the 3.8 and 4.2 development streams.
-See the <a href="buildNotes.php">build notes</a> for details about bugs fixed and other changes.</p>
-<nav id="header-links">
-<ul>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#Equinox">Equinox</a></li>
-</ul>
-</nav>
-
-<section id="news-content">
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr id="javadoc-hover-parameter-annotations">
-    <td class="title">Javadoc hover shows parameter annotations</td>
-    <td class="content">
-        Javadoc hovers now render the annotations on method parameters:
-        <p><img src="images/javadoc-hover-parameter-annotations.png" alt="org.eclipse.User.User(@NonNull String name, int uid, @Nullable String email)"/></p>
-    </td>
-  </tr>
-
-  <tr id="annotation-null-analysis">
-    <td class="title">Annotation-based null analysis</td>
-    <td class="content">
-        JDT can now be configured to use annotations designated as null annotations to 
-		perform enhanced inter-procedural null analysis. This feature can be enabled in
-		
-		<b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; Null analysis</b>:
-		<p><img src="images/null-prefs.png" alt="Errors/Warnings preference page with 'Enable annotation-based null analysis' highlighted"/></p>
-		
-		<p> You can use either the default annotations bundled with JDT or use your own annotations
-		as null annotations. In addition to enabling the null analysis, the annotations need to be on the 
-		Java build path of your project. The default annotations can be found in the <b>org.eclipse.jdt.annotation</b> JAR
-		in the <code>plugins</code> directory, which can be consumed as an OSGi bundle or plain JAR.</p>
-		<p>When annotation-based null analysis is enabled, JDT issues new diagnostics based on the nullness
-			of a variable or a method return type as specified by a null annotation.</p>
-		
-		<p><img src="images/null-annotation-problems1.png" alt="	public void foo(@NonNull Object o1) {
-		System.out.println(o1.toString()); // OK: o1 cannot be null
-	}
-	
-	@NonNull Object bar(@Nullable String s1) {
-		foo(null); // cannot pass null argument
-		@NonNull String s= null; // cannot assign null value 
-		@NonNull String t= s1; // cannot assign potentially null value 
-		return null; // cannot return null value
-	}"/></p>
-		<p> Similar diagnostics are also elicited when the value assigned/returned may potentially be null or has unknown nullness.</p>
-		
-		<p> Overriding methods are also checked for correctness:</p>
-		<p><img src="images/null-annotation-problems2.png" alt="class Base {
-	@NonNull Object method(@Nullable Object o) {
-		return new Object();
-	}
-}
-
-class Sub extends Base {
-	@Override            // method parameter must allow null
-	@Nullable Object method(@NonNull Object o) {
-		return new Object();
-	}
-}"/></p>
-
-		<p> You can also use the <code>@NonNullByDefault</code> annotation to set a global default on an element (package, type, method) for all enclosed elements.</p>
-		<p><img src="images/null-annotation-problems-redundant1.png" alt="@NonNullByDefault
-class MyClass {
-	// redundant @NonNull annotations:
-	public @NonNull Object foo(@NonNull Object o) {
-		return o;
-	}
-	
-	@NonNullByDefault(false) // cancels the default
-	Object bar(@NonNull Object o) {
-		return o;
-	}
-}"/></p>
-
-		<p> As a result of annotating method signatures, the existing intra-procedural null analysis has even more information
-		because of user-specified annotations and thus provides better results. In the example below, the compiler would not have
-		been able to evaluate the null status of parameter 'obj' without the null annotation.</p>
-		<p><img src="images/null-annotation-problems-redundant2.png" alt="public void foo(@NonNull Object obj) {
-		if (obj == null) { }
-	}"/></p>
-		
-		<p><b>Note:</b> This is the first version of this feature. We are working on making this
-		easier to consume in Java project setups, and we will also add quick fixes.
-		The implemented features are complete and tested, but e.g. support for annotating fields or
-		APIs from third-party libraries is currently missing.
-		</p>
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-
-  <tr id="custom-target-locations">
-    <td class="title">Custom target locations</td>
-    <td class="content">
-	You can now provide custom locations for target definitions.  They appear in both the target 
-	definition editor and wizard along with the platform provided target locations: directory, installation, 
-	feature and software site.
-	<p>To provide a custom location, you must implement <tt>ITargetLocation</tt> and extend the extension point 
-	<tt>org.eclipse.pde.core.targetLocations</tt>.  To provide labels, wizards and other user interface elements, 
-	you must extend an additional extension point <tt>org.eclipse.pde.ui.targetLocationProvisioners</tt> and have 
-	your <tt>ITargetLocation</tt> implementation adapt to several types.  For additional details, view the Javadoc on 
-	<tt>ITargetLocation</tt>.</p>
-	</td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-
-	<tr id="swt-tree-cursor">
-      <td class="title">Tree Cursor</td>
-      <td class="content">
-      The new <tt>TreeCursor</tt> class can be used to enable users to navigate a <tt>Tree</tt> control's individual 
-      cells, similar to what <tt>TableCursor</tt> makes possible for <tt>Table</tt> controls.  For an example of 
-      using <tt>TreeCursor</tt> see <a href="http://git.eclipse.org/c/platform/eclipse.platform.swt.git/plain/examples/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet360.java">Snippet360</a>.
-      <p><img src="images/treecursor.png" alt="Tree Cursor"></p>
-      </td>
-  </tr>
-  <tr id="swt-vo-context-menu">
-      <td class="title">VoiceOver context menu</td>
-      <td class="content">
-      On Mac, you can now use the keyboard to open a context menu when VoiceOver is running,
-      using the standard VoiceOver key sequence Control+Option+Shift+M.
-      </td>
-    </tr>
-
-  <tr id="context-menu-shortcut">
-    <td class="title">Shortcut for context menu on the Mac</td>
-    <td class="content">
-      <b>Shift+F10</b> now also opens the context menu on the Mac, like it already works on most other platforms.
-      The key binding of the new <b>Show Context Menu</b> command can be configured on the <b>General &gt; Keys</b> preference page.
-      <p><img src="images/context-menu.png" alt="Screenshot of a context menu in the Synchronize view"/></p>
-    </td>
-  </tr>
-
-  <tr id="cvs-sync-filters">
-    <td class="title">Filters in CVS Sync View</td>
-    <td class="content">
-      You can now use regular expressions to filter out changes in the CVS <b>Synchronize</b> view. 
-      To enable filters go to <b>Preferences > General > Team > CVS > Synchronize/Compare</b>, 
-      uncheck <b>Only look at timestamps to detect changes</b> and enter your regex pattern 
-      in the <b>Regular expression to ignore changes in synchronizations</b> field. Each difference 
-      in a change is checked against the pattern and is considered as matched, if either left or right side 
-      of the difference matches. If all diffs in a file match, the file is excluded from the view.
-      <p>
-        <img src="images/filters-in-cvs-syncview.png" alt="Preferences for filters in CVS Sync View ">
-      </p>
-    </td>
-  </tr>
-
-  <tr id="flexible-viewer-refactor">
-    <td class="title">Flexible viewer refactored</td>
-    <td class="content">
-      The code driving the debug views (Debug, Variables and Breakpoints) has been substantially refactored to improve its overall quality, stability and
-      performance. 
-      <br><br>
-      Some of the more notable changes include:
-      <ul>
-        <li>There is a 30% improvement in the overall performance of the views</li>
-        <li>Two new interfaces have been added to the provisional API: <code>IModelProxyFactory2</code> and <code>ITreeModelViewer</code></li>
-        <li>The <b>Copy</b> and <b>Find</b> actions have been re-written to work better with the virtual views</li>
-        <li>A new viewer filter extension has been added to <code>TreeModelViewerFilter</code>, mitigating scrollbar presentation issues</li>
-      </ul> 
-      The complete list of changes can be found <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=161435#c47">here</a>.
-    </td>
-  </tr>
-  <tr id="first-item">
-    <td class="title">Welcome is back (4.2 only)</td>
-    <td class="content">
-      As we progress towards release, the number of missing bits of Eclipse functionality in Eclipse 4.x continue 
-      to shrink. For this milestone we've done the preliminary work on both the Capabilities / Activities implementation
-      as well as re-enabling the <b>Welcome</b> (aka "Intro") screen.
-      <p>
-      This is a <i>major</i> milestone for 4.2 since these were the last two major functional areas which were missing 
-      compared to the 3.x stream. With three remaining milestones to fix and polish it looks like we're in good shape for Juno.
-      </p>
-      <p>
-      <strong>NOTE:</strong> The first time you start up M4 (even on an existing workspace) you will see the Welcome 
-      screen. This is not a defect; it's just the first time that the 'Intro' code has been run on that workspace. 
-      If you have more than one perspective open, you'll also notice there is a layout problem that will be
-      addressed in the next milestone. In either case you can just close or un-maximize the Welcome view to get back to normal.
-      </p>
-      <p>
-        <img src="images/intro.png" alt="Welcome perspective in Eclipse 4.2">
-      </p>
-    </td>
-  </tr>
-
-  <tr id="workbench-events-refactoring">
-    <td class="title">Refactored Eclipse 4 Event API (4.2 only)</td>
-    <td class="content">
-      Workbench UI events have been refactored to make them easier to understand and use.  
-      For a detailed write up on the Eclipse 4 event model and the changes in this release 
-      please take a look at <a href="http://wiki.eclipse.org/Eclipse4/RCP/Event_Model">http://wiki.eclipse.org/Eclipse4/RCP/Event_Model</a> and 
-      <a href="http://wiki.eclipse.org/Eclipse4/UI/Event/Migration">http://wiki.eclipse.org/Eclipse4/UI/Event/Migration</a>.
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="Equinox">Equinox</td>
-  </tr>
-
-  <tr id="jetty">
-    <td class="title">Update to Jetty 8 and Servlet 3.0</td>
-
-    <td class="content">
-      The Equinox HTTP service implementation is now using Jetty 8.1 as the
-      web container to support Servlet 3.0 and JSP 2.2.  The Equinox HTTP
-      service is required to host the Eclipse user assistence web context
-      for serving up help content.
-      <p>
-      For the Juno release, Equinox will no longer support the use of older
-      Jetty implementations and we are no longer shipping Jetty 6.  The
-      Equinox HTTP service implementation will no longer work with the
-      Servlet 2.5 and JSP 2.1 APIs.  Also note that the 
-      Jasper and expresson language implementation bundles
-      have changed in order to support the Servlet 3.0 and JSP 2.2 
-      specifications.  The following bundles have been removed:
-      <ul>
-        <li>org.apache.jasper</li>
-        <li>org.apache.commons.el</li>
-        <li>org.mortbay.jetty.server</li>
-        <li>org.mortbay.jetty.util</li>
-      </ul>
-      These have been replaced with the following to support Servlet 3.0
-      and JSP 2.2:
-      <ul>
-        <li>org.eclipse.jetty.continuation</li>
-        <li>org.eclipse.jetty.http</li>
-        <li>org.eclipse.jetty.io</li>
-        <li>org.eclipse.jetty.security</li>
-        <li>org.eclipse.jetty.server</li>
-        <li>org.eclipse.jetty.servlet</li>
-        <li>org.eclipse.jetty.util</li>
-        <li>javax.el</li>
-        <li>org.apache.jasper.glassfish</li>
-        <li>com.sun.el</li>
-      </ul>
-      </p>
-    </td>
-  </tr>
-
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-</section>
-<aside>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Juno milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M3-201110281100/eclipse-news-M3.html">New for Eclipse Juno milestone build M3 (October 28, 2010)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M2-201109161615/eclipse-news-M2.html">New for Eclipse Juno milestone build M2 (September 16, 2010)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops/S-3.8M1-201108031800/eclipse-news-M1.html">New for Eclipse Juno milestone build M1 (August 5, 2011)</a></li>
-</ul>
-</aside>
-</body>
-</html>
diff --git a/platform/4.2/M4/images/context-menu.png b/platform/4.2/M4/images/context-menu.png
deleted file mode 100644
index 864d9cc..0000000
--- a/platform/4.2/M4/images/context-menu.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M4/images/filters-in-cvs-syncview.png b/platform/4.2/M4/images/filters-in-cvs-syncview.png
deleted file mode 100644
index 3052012..0000000
--- a/platform/4.2/M4/images/filters-in-cvs-syncview.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M4/images/intro.png b/platform/4.2/M4/images/intro.png
deleted file mode 100644
index 8dca8f8..0000000
--- a/platform/4.2/M4/images/intro.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M4/images/javadoc-hover-parameter-annotations.png b/platform/4.2/M4/images/javadoc-hover-parameter-annotations.png
deleted file mode 100644
index 94368fd..0000000
--- a/platform/4.2/M4/images/javadoc-hover-parameter-annotations.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M4/images/null-annotation-problems-redundant1.png b/platform/4.2/M4/images/null-annotation-problems-redundant1.png
deleted file mode 100644
index 9af2519..0000000
--- a/platform/4.2/M4/images/null-annotation-problems-redundant1.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M4/images/null-annotation-problems-redundant2.png b/platform/4.2/M4/images/null-annotation-problems-redundant2.png
deleted file mode 100644
index df3dc72..0000000
--- a/platform/4.2/M4/images/null-annotation-problems-redundant2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M4/images/null-annotation-problems1.png b/platform/4.2/M4/images/null-annotation-problems1.png
deleted file mode 100644
index 0e17d44..0000000
--- a/platform/4.2/M4/images/null-annotation-problems1.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M4/images/null-annotation-problems2.png b/platform/4.2/M4/images/null-annotation-problems2.png
deleted file mode 100644
index a55bf91..0000000
--- a/platform/4.2/M4/images/null-annotation-problems2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M4/images/null-prefs.png b/platform/4.2/M4/images/null-prefs.png
deleted file mode 100644
index d2794b2..0000000
--- a/platform/4.2/M4/images/null-prefs.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M4/images/treecursor.png b/platform/4.2/M4/images/treecursor.png
deleted file mode 100644
index 05d6577..0000000
--- a/platform/4.2/M4/images/treecursor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/default_style.css b/platform/4.2/M5/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.2/M5/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.2/M5/eclipse-news-M5.html b/platform/4.2/M5/eclipse-news-M5.html
deleted file mode 100644
index 2a7c1bc..0000000
--- a/platform/4.2/M5/eclipse-news-M5.html
+++ /dev/null
@@ -1,202 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse 3.8 and 4.2 M5 News</title>
-</head>
-<body>
-<h1>Eclipse 3.8 and 4.2 M5 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M5 
-  (January 27, 2012) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-Unless otherwise indicated, all entries listed here are available in both the 3.8 and 4.2 development streams.
-See the <a href="buildNotes.php">build notes</a> for details about bugs fixed and other changes.</p>
-<ul>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#PDE">PDE</a></li>
-  <li><a href="#Equinox">Equinox</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr id="null-anaylsis-fields">
-    <td class="title">Null analysis for fields</td>
-    <td class="content">
-        JDT can now raise null related errors/warnings for fields. You can configure null analysis for 
-		fields in 
-		<b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; Null analysis</b>.
-		<p><img src="images/null-analysis-prefs.png" alt="Errors/Warnings preference page with 'Include fields in null analysis' highlighted"/></p>
-        
-		With this option enabled, you will be able to see null related errors/warnings on fields, 
-		configured using the options <b>Null Pointer access</b>, 
-		<b>Potential null pointer access</b> and <b>Redundant null check</b>. Some examples are given below
-		<ul>
-		<li><b>Null pointer access warning</b>
-		<p><img src="images/npe-constant-field.png" alt="null pointer access warning on dereferencing a constant field with a null value"/></p>
-		</li>
-		<li><b>Potential null pointer access warnings</b>
-		<p><img src="images/pot-npe-field.png" alt="potential null pointer access warning on a field that may be null"/></p>
-		<p>Note that in the above case, the field <code>field1</code> is considered only potentially null because it may be modified in other threads</p>
-		<p><img src="images/pot-npe-constant-field.png" alt="potential null pointer access warning on a constant field that may be null"/></p>
-		</li>
-		<li><b>Redundant null check warnings</b>
-		<p><img src="images/redundant-null-constant-field.png" alt="redundant null check warning on comparing a constant field with a null value against null"/></p>
-		<p><img src="images/redundant-null-constant-field2.png" alt="redundant null check warning on comparing a constant field with a non-null value against non-null"/></p>
-		<p><img src="images/always-false-null-comparison.png" alt="always false null comparison warning on comparing a constant field with a null value against non-null"/></p>
-		<p><img src="images/redundant-field-instanceof.png" alt="redundant instanceof warning on a constant field with a null value"/></p>
-		</li>
-		</ul>
-		<p>This option can be enabled for the command line batch compiler using the <code>-warn:<b>+nullFields</b></code> option.</p>
-    </td>
-  </tr>
-  
-  <tr id="batch-compiler-null-annotations">
-    <td class="title">Batch compiler options for using null annotations</td>
-    <td class="content">
-        You can now configure the batch compiler to use annotations for null analysis by passing the token <b>nullAnnot(nullable|nonnull|nonnullbydefault)</b> to the <code>-warn</code> option, 
-		where nullable, nonnull and nonnullbydefault are the fully qualified names of the annotation types to be used for null analysis. You can use <b>nullAnnot</b> alone
-		to use JDT's default annotations.
-		<p>In addition, you can use the <b>-nonNullByDefault</b> token to globally use nonnull as the default when
-		annotation-based null analysis is enabled. This implies that all types in method signatures without a null annotation are considered as specified non-null.</p>
-	</td>
-  </tr>
-  
-  <tr id="resource-leak-warnings-changes">
-    <td class="title">Smarter resource leak detection</td>
-    <td class="content">
-        JDT now performs smarter analysis so that resource leak related errors/warnings 
-		(configured by the options <b>Resource leak</b> and <b>Potential resource leak</b>
-		in <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; Potential programming problems</b>) are no longer 
-		reported on practically unimportant cases. Some examples where the absence of a close() call does not
-		trigger any error/warning are given below:
-		<ul>
-		<li> Resource-less implementors of Closeable, such as StringReader.
-		<p><img src="images/os-less-unclosed-resource.png" alt="no resource leak reported if resource-less implentor of Closeable is not closed"/></p>
-		</li>
-		<li> Wrapping implementors of Closeable, such as BufferedReader, that simply wrap a resource-less Closeable, directly or indirectly.
-		<p><img src="images/wrapped-os-less-unclosed-resource.png" alt="no resource leak reported when a resource which wraps a resource-less implentor of Closeable is not closed"/></p>
-		</li>
-		<li> Wrapped resources where any resource in the chain is (potentially) closed.
-		<p><img src="images/wrapped-resource.png" alt="potential resource leak reported when any resource in the chain of wrapper resources is closed along some execution path."/></p>
-		</li>
-		</ul>
-	</td>
-  </tr>
-  
-  <tr id="encoding-for-source-attachments">
-    <td class="title">Encoding for source attachments</td>
-    <td class="content">
-        You can now specify the encoding for source attachments for libraries e.g.
-		in <b>Build Path &gt; Libraries &gt;</b> expand the library <b>&gt; Source attachment &gt; Edit...</b>
-		<p><img src="images/source-attachment-encoding.png" alt="Dialog to specify encoding for source attachments."/></p>
-	</td>
-  </tr>
-  
-  <tr id="pre-built-index-support">
-    <td class="title">Faster search with pre-built indexes</td>
-    <td class="content">
-        <i>Note: This feature is mainly intended for plug-ins that implement their own classpath container, not for the end user.</i>
-        <p>You can now tell JDT search to use pre-built indexes instead of having the compiler generate the indexes the first time a JAR is added to the classpath. 
-		This prevents indexing from occurring on the user's machine and lets the user obtain first search results faster.</p>
-		<p>You can specify the index file as a classpath attribute <code>IClasspathAttribute.INDEX_LOCATION_ATTRIBUTE_NAME</code> of the library.</p>
-		<p>See <b>Help &gt; JDT Plug-in Developer Guide &gt; Programmer's Guide &gt; JDT Core &gt; Indexes for the Java search</b> for more details.</p>
-	</td>
-  </tr>
-
-  <tr id="export-detail-formatters">
-    <td class="title">Export detail formatters</td>
-    <td class="content">
-        Detail formatters can now be exported as separate preferences. Previously the only way to share detail formatters was to export
-        all of your workspace settings.    
-        <p><img src="images/detail-formatters.png" alt="Detail formatters in the export dialog"/></p>
-    </td>
-  </tr>
-
-  <tr id="jdt-debug-15-ee">
-    <td class="title">JDT Debug requires a 1.5 EE</td>
-    <td class="content">
-       JDT Debug has been moved up to now require a 1.5 execution environment
-    </td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  <tr id="screenshots">
-    <td class="title">Shared area tab navigation</td>
-    <td class="content">
-        Navigation arrows have been introduced to the sides of the shared area to allow
-        you to click and view the tabs that are to the left and right of the currently
-        selected tab. This is the default setting on new installations. Switching to the
-        Classic theme from the preferences (<b>Preferences &gt; General &gt; Appearance</b>)
-        will allow you to bring back the MRU behaviour from 3.x. The MRU behaviour can
-        also be toggled on and off via CSS by setting the <code>mru-visible</code> attribute
-        of an <code>MPartStack</code> to <code>true</code> or <code>false</code>.
-
-      <p>This is a preliminary form of the feature and your feedback would be most appreciated.</p>
-
-      <p><img src="images/tab-navigation.png" alt="The shared area with left and right navigation
-        arrows on its sides."/></p></td>
-  </tr>
-  <tr id="edit-multi-line-vars">
-    <td class="title">Improved editing of environment variables</td>
-    <td class="content">
-        In 3.8M5, editing multi-line environment variables became much simpler with a new UI that presents the variables in a scrolling text widget.
-        The new UI can be found in the edit dialog for a multi-line environment variable on the <b>Environment</b> tab of a supporting launch configuration.
-        <p><img src="images/multi-env-var.png" alt="New edit dialog for multi-line environment variables"/></p>
-    </td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  <tr id="TracingPage">
-      <td class="title">Tracing preference page</td>
-      <td class="content">
-        A new preference page is available to dynamically set the debug tracing options for Eclipse.  You can turn on individual tracing options and the changes will take effect immediately.  There is no need to restart Eclipse.
-
-	<p><img src="images/tracing.png" alt="Tracing preference page"/></p>
-
-	<p>To add a plug-in's tracing options to the page, you must provide an <code>org.eclipse.ui.trace.traceComponents</code> extension. Your bundle must also register an <code>org.eclipse.osgi.service.debug.DebugOptionsListener</code> to be notified when tracing options are changed.</p>
-
-	<p>The preference page can be included in other products.  It is contained in the <code>org.eclipse.ui.trace</code> plug-in and has no dependencies on PDE.</p>
-
-      </td>
-  </tr>
-
-  <tr id="NonJarTargetPlugins">
-      <td class="title">Non *.jar plug-ins in target platform</td>
-      <td class="content">
-	The target platform will now recognize archive files with any file extension as long as they contain a manifest with the necessary OSGi headers. Previously, PDE only supported directory plug-ins and jarred (*.jar) plug-ins.
-      </td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="Equinox">Equinox</td>
-  </tr>
-  <tr id="pref-storage">
-    <td class="title">Customize storage for preference scopes</td>
-    <td class="content">
-      When defining your own preference scope, you can now extend a simple storage
-      customization class rather than implementing all the preference logic yourself. In this class you
-      simply define the code to read and write a preference node to whatever backing store you want to use.
-      This makes it very easy to define a custom preference scope with alternate storage
-      requirements. For more details see the documentation for the <tt>org.eclipse.equinox.preferences.preferences</tt>
-      extension point, or the new API class <tt>org.eclipse.core.runtime.preferences.AbstractPreferenceStorage</tt>.
-    </td>
-  </tr>
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Juno milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M4-201112092100/eclipse-news-M4.html">New for Eclipse Juno milestone build M4 (December 9, 2010)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M3-201110281100/eclipse-news-M3.html">New for Eclipse Juno milestone build M3 (October 28, 2010)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M2-201109161615/eclipse-news-M2.html">New for Eclipse Juno milestone build M2 (September 16, 2010)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops/S-3.8M1-201108031800/eclipse-news-M1.html">New for Eclipse Juno milestone build M1 (August 5, 2011)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.2/M5/images/always-false-null-comparison.png b/platform/4.2/M5/images/always-false-null-comparison.png
deleted file mode 100644
index a62fcba..0000000
--- a/platform/4.2/M5/images/always-false-null-comparison.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/detail-formatters.png b/platform/4.2/M5/images/detail-formatters.png
deleted file mode 100644
index 84b2dac..0000000
--- a/platform/4.2/M5/images/detail-formatters.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/multi-env-var.png b/platform/4.2/M5/images/multi-env-var.png
deleted file mode 100644
index 9560711..0000000
--- a/platform/4.2/M5/images/multi-env-var.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/npe-constant-field.png b/platform/4.2/M5/images/npe-constant-field.png
deleted file mode 100644
index 1336bf5..0000000
--- a/platform/4.2/M5/images/npe-constant-field.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/null-analysis-prefs.png b/platform/4.2/M5/images/null-analysis-prefs.png
deleted file mode 100644
index 15818a1..0000000
--- a/platform/4.2/M5/images/null-analysis-prefs.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/os-less-unclosed-resource.png b/platform/4.2/M5/images/os-less-unclosed-resource.png
deleted file mode 100644
index 525504a..0000000
--- a/platform/4.2/M5/images/os-less-unclosed-resource.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/pot-npe-constant-field.png b/platform/4.2/M5/images/pot-npe-constant-field.png
deleted file mode 100644
index 64af2d0..0000000
--- a/platform/4.2/M5/images/pot-npe-constant-field.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/pot-npe-field.png b/platform/4.2/M5/images/pot-npe-field.png
deleted file mode 100644
index e6be559..0000000
--- a/platform/4.2/M5/images/pot-npe-field.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/redundant-field-instanceof.png b/platform/4.2/M5/images/redundant-field-instanceof.png
deleted file mode 100644
index b962842..0000000
--- a/platform/4.2/M5/images/redundant-field-instanceof.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/redundant-null-constant-field.png b/platform/4.2/M5/images/redundant-null-constant-field.png
deleted file mode 100644
index 95a0083..0000000
--- a/platform/4.2/M5/images/redundant-null-constant-field.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/redundant-null-constant-field2.png b/platform/4.2/M5/images/redundant-null-constant-field2.png
deleted file mode 100644
index 85b75c1..0000000
--- a/platform/4.2/M5/images/redundant-null-constant-field2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/source-attachment-encoding.png b/platform/4.2/M5/images/source-attachment-encoding.png
deleted file mode 100644
index b7e0447..0000000
--- a/platform/4.2/M5/images/source-attachment-encoding.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/tab-navigation.png b/platform/4.2/M5/images/tab-navigation.png
deleted file mode 100644
index 6628db3..0000000
--- a/platform/4.2/M5/images/tab-navigation.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/tracing.png b/platform/4.2/M5/images/tracing.png
deleted file mode 100644
index a585ad6..0000000
--- a/platform/4.2/M5/images/tracing.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/wrapped-os-less-unclosed-resource.png b/platform/4.2/M5/images/wrapped-os-less-unclosed-resource.png
deleted file mode 100644
index 5138fe9..0000000
--- a/platform/4.2/M5/images/wrapped-os-less-unclosed-resource.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M5/images/wrapped-resource.png b/platform/4.2/M5/images/wrapped-resource.png
deleted file mode 100644
index 293b81b..0000000
--- a/platform/4.2/M5/images/wrapped-resource.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/default_style.css b/platform/4.2/M6/default_style.css
deleted file mode 100644
index fe3f8a2..0000000
--- a/platform/4.2/M6/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr .section {font-size: 20px; font-weight: bold;}
-table.news tr .title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr .content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.2/M6/eclipse-news-M6.html b/platform/4.2/M6/eclipse-news-M6.html
deleted file mode 100644
index d936c69..0000000
--- a/platform/4.2/M6/eclipse-news-M6.html
+++ /dev/null
@@ -1,447 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse 3.8 and 4.2 M6 News</title>
-</head>
-<body>
-<h1>Eclipse 3.8 and 4.2 M6 - New and Noteworthy</h1>
-<p>While there were lineups outside tech stores around the world today for a 
-shiny new piece of <a href="http://arstechnica.com/apple/news/2012/03/ipad-3-teardown-my-god-its-full-of-lithium-ions.ars">fruit</a>,
-today is also notable for a new stable build towards the <a href="http://wiki.eclipse.org/Juno">Juno</a> release
-of the Eclipse platform. Here are some of the more noteworthy things available in milestone build M6 
-  (March 16, 2012) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-Unless otherwise indicated, all entries listed here are available in both the 3.8 and 4.2 development streams.
-See the <a href="buildNotes.php">build notes</a> for details about bugs fixed and other changes.</p>
-<ul>
-  <li><a href="#Equinox">Equinox</a></li>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Equinox">Equinox</td>
-  </tr>
-  <tr id="osgi-core-5">
-    <td class="title">OSGi Core Release 5</td>
-    <td class="content">
-      With this milestone the Equinox OSGi Framework implements the 
-      draft OSGi Core Release 5 (R5) specification.  The OSGi Core 
-      R5 specification is an incremental change from the R4.3 
-      specification.  A majority of the changes included in
-      the Core R5 specification are in support of the upcoming
-      OSGi Enterprise Release 5 specification.  A public draft of
-      the specification will be available 
-      <a href="http://www.osgi.org/Specifications/Drafts">here</a>
-      by March 26, 2012.  The final version will be available 
-      <a href="http://www.osgi.org/Download/File?url=/download/osgi.core-5.0.0-pfd.pdf">here</a>
-      shortly after that.
-    </td>
-  </tr>
-  <tr id="publisher-negation-requirements">
-    <td class="title">Publisher Support for Negation Requirements</td>
-    <td class="content">
-      The p2 publisher can now publish <b>negation</b> requirements.
-      A negation requirement is a requirement that <b>must not</b>
-      be present.  For example, the Rich Ajax Platform (RAP) can 
-      declare a negation requirement on the Eclipse Platform, meaning
-      that RAP won't be installable into your IDE.<br/>
-      Negation requirements are specified using the p2.inf file.  
-      Details are available on the <a href="http://wiki.eclipse.org/Equinox/p2/Customizing_Metadata#Capability_Advice:">Wiki</a>
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-
-  <tr id="XULRunner">
-    <td class="title"> XULRunner 10</td>
-    <td class="content">
-      The SWT browser now supports embedding XULRunner 10.0.x (note that XULRunner versions 4.x - 9.x are not supported).  
-      Apps wishing to use this must ship a XULRunner 10 runtime and explicitly point at it as described in 
-      <a href="http://www.eclipse.org/swt/faq.php#specifyxulrunner">the FAQ</a> .
-    </td>
-  </tr>
- 
-  <tr id="ContextMenuTrigger">
-    <td class="title">Provide context menu trigger</td>
-    <td class="content">
-      <tt>MenuDetectEvent</tt> now fills in the event <tt>detail</tt> field to indicate
-      whether the context menu is being triggered by the <tt>SWT.MENU_MOUSE</tt> or <tt>SWT.MENU_KEYBOARD</tt>.
-      If the <tt>event.detail</tt> is <tt>SWT.MENU_KEYBOARD</tt>, custom controls can appropriately position
-      the context menu based on current focus or selection.
-    </td>
-  </tr>
-  <tr id="CustomColors">
-    <td class="title">Set/get custom colors in ColorDialog</td>
-    <td class="content">
-      <tt>ColorDialog</tt> now supports <tt>getRGBs()</tt> and <tt>setRGBs(RGB [])</tt> to allow applications
-      to retrieve, save, and restore any custom colors that the user selected in the dialog.
-      <p><img src="images/custom-colors.png" alt="Custom Colors section of a win32 ColorDialog"></p>
-    </td>
-  </tr>
-
-  <tr id="BIDI">
-    <td class="title">BIDI segments on text widget</td>
-    <td class="content">
-      The <tt>Text</tt> widget now supports adding <tt>SegmentListener</tt> for BIDI support. This allows BIDI ordering to be applied to segments of the text instead of the entire text.
-    </td>
-  </tr>
-  
-  <tr id="Browser">
-    <td class="title">Browser Function Access</td>
-    <td class="content">
-      <tt>BrowserFunction</tt> can now be installed into specific frames.
-    </td>
-  </tr>
-  
-  <tr id="JarLoading">
-    <td class="title">SWT Runtime introspection</td>
-    <td class="content">
-      <tt>SWT.isLoadable()</tt> can be used to determine whether the SWT implementation can be loaded in the current running environment.
-    </td>
-  </tr>
-
-  <tr id="Overlay">
-    <td class="title">Overlay scrollbars</td>
-    <td class="content">
-      <tt>Scrollable.getScrollbarsMode()</tt> can be used to determine whether the platform shows overlay scrollbars.
-    </td>
-  </tr>
-
-  <tr id="relaunchlast-api">
-    <td class="title">RelaunchLastAction has been made API</td>
-    <td class="content">
-      The internal class <code>RelaunchLastAction</code> has been promoted to API and can be found in the 
-      <code>org.eclipse.debug.ui.actions</code> package.
-    </td>
-  </tr>
-
-  <tr id="expression-view-constant-api">
-    <td class="title">Add new expression image constant has been made API</td>
-    <td class="content">
-      The constant <code>IDebugUIConstants.IMG_OBJ_ADD_NEW_EXPRESSION</code> has been added to API to allow consumers who 
-      extend or use the <b>Expressions</b> view look-and-feel to use the <b>Add New Expression</b> icon 
-      (<img src="images/monitorexpression_tsk.gif" alt="The add new expression icon"/>).
-    </td>
-  </tr>
-
-  <tr id="toggle-bp-target-mgr-api">
-    <td class="title">Toggle breakpoints target manager has been made API</td>
-    <td class="content">
-      The interface <code>org.eclipse.debug.ui.actions.IToggleBreakpointsTargetManager</code> has been made API to allow clients
-      access to known <code>IToggleBreakpointTarget</code>s. The new API can be accessed via 
-      <code>org.eclipse.debug.ui.DebugUITools#getToggleBreakpointsTargetManager()</code>
-    </td>
-  </tr>
-  
-  <tr id="bp-types-contribution-api">
-  	<td class="title">BreakpointTypesContribution has been made API</td>
-  	<td class="content">
-  		The class <code>org.eclipse.debug.ui.actions.BreakpointTypesContribution</code> has been added to API. This class 
-  		can be reused by clients to add a breakpoint type action in the editor gutter context menu to match the action(s) that appear in the 
-  		<b>Run &gt; Breakpoint Types</b> menu. 
-  	</td>
-  </tr>
-
-  <tr id="var-view-find-override">
-  	<td class="title">Find action can be customised in Variables View specialisations</td>
-  	<td class="content">
-  		Consumer now have the ability to completely override the behaviour of the <b>Find...</b> action in the <b>Variables View</b> and any of
-  		its sub-classes, e.g. <b>Expressions View</b>, <b>Modules View</b>, etc.
-  		<p>
-  			To replace the default <b>Find...</b> actions clients must provide an adapter for the 
-  			interface <code>org.eclipse.debug.internal.ui.viewers.model.provisional.IViewActionProvider</code>.
-  		</p>
-  		<p>
-  			For more information see the Javadoc for <code>org.eclipse.debug.internal.ui.viewers.model.provisional.IViewActionProvider</code>
-  			with an example available in the <code>org.eclipse.debug.examples.ui</code> bundle found in the Platform Debug Git repo.
-  		</p>
-  	</td>
-  </tr>
-  <tr id="launch-config-name-validation">
-  	<td class="title">Improved launch configuration name validation</td>
-  	<td class="content">
-  		Now if you create a launch configuration with the name of an existing configuration, the type of the conflicting configuration
-  		is noted in the error message.
-  		<p><img src="images/lcd-name-error.png" alt="Launch configuration dialog showing name conflict error"/></p>
-  	</td>
-  </tr>
-  
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  
-  <tr id="ignore-warnings-source-folders">
-    <td class="title">Selectively ignore errors/warnings from source folders</td>
-    <td class="content">
-        You can now configure JDT to ignore optional errors/warnings from certain source folders. 
-		<b>Project properties &gt; Java Build Path &gt; Compiler &gt; Source</b>.
-		<p><img src="images/ignore-warnings-source-folders.png" alt="Java Build path page with 'Ignore optional compile problems' highlighted"/></p>
-        <p>
-		With this option set to <b>Yes</b>, JDT will suppress errors/warnings configured in the 
-		<b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings</b> page. This can be desirable
-		for source folders that contain auto-generated classes or tests.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="quick-outline-camel-case">
-    <td class="title">CamelCase in Quick Outline</td>
-    <td class="content">
-        The <b>Quick Outline (Ctrl+O)</b> and <b>Quick Hierarchy (Ctrl+T)</b> in the Java Editor now also
-        support camelCase matching on the element name, quite similar to the Open Type dialog and Content Assist.
-		<p><img src="images/quick-outline-camel-case.png" alt="Quick Outline of StyledText with pattern 'gCa'"/></p>
-		The * and ? wildcards still work, of course.
-    </td>
-  </tr>
-  
-  <tr id="improved-null-analysis-problems">
-    <td class="title">Improved messages for null analysis problems</td>
-    <td class="content">
-        The wording of several error messages and compiler options in
-        <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; Null analysis</b> has been improved:
-		<ul>
-		<li><b>Violation of null specification</b><br/>
-			<img src="images/new-null-analysis-message1.png" alt="This option produces the
-			'Null type mismatch: required '@NonNull String' but the provided value is specified as @Nullable' warning"/>
-			<p>Here, 'in' is not a legal return value because of the @Nullable annotation in its <b>declaration</b>.</p>
-		</li>
-		<li><b>Conflict between null annotations and null inference</b><br/>
-			<img src="images/new-null-analysis-message2.png" alt="This option produces the
-			'Null type mismatch: required @NonNull String but the provided value is inferred as @Nullable' warning"/>
-			<p>Here, 'local' is not a legal return value, because flow analysis for the un-annotated variable 'local' <b>infers</b> that 
-			it can be null on some path.</p>
-		</li>
-		<li><b>Unchecked conversion from non-annotated type to @NonNull type</b><br/>
-			<img src="images/new-null-analysis-message3.png" alt="This option produces the
-			'Null type safety: The expression of type String needs unchecked conversion to conform to @NonNull String' warning"/>
-			<p>Here, the return value from 'getLegacyValue()' may or may not be compatible to '@NonNull String'. 
-			Similar to converting a legacy raw type to a generic type, also here essential type information is missing 
-			since 'getLegacyValue()' has no @NonNull or @Nullable annotation.</p>
-		</li>
-		</ul>
-	</td>
-  </tr>
-  
-  <tr id="missing-non-null-by-default-annotation">
-    <td class="title">Detection of missing default nullness annotation</td>
-    <td class="content">
-        You can now configure JDT to detect a missing default nullness annotation when using the annotation-based null analysis.
-        When <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; Null analysis &gt; Missing '@NonNullByDefault' annotation on package</b>
-        is enabled, JDT will issue an error/warning in the following cases:
-		<ul>
-		<li> When a package does not contain an '@NonNullByDefault' annotation in the package-info.java:
-		<p><img src="images/missing-nonnullbydefault-package.png" alt="Missing @NonNullByDefault annotation on package warning"/></p>
-		</li>
-		<li> When a type inside a default package does not contain a default nullness annotation.
-		<p><img src="images/missing-nonnullbydefault-type.png" alt="Missing @NonNullByDefault annotation on type warning"/></p>
-		</li>
-		</ul>
-		<p> Note that the option <b>Use non-null as workspace wide (or project-wide) default</b> has been withdrawn. 
-		Instead, you can enable the <b>Missing '@NonNullByDefault' annotation on package</b> option and make sure you specify the default nullness 
-		annotation on all types/packages.</p>
-	</td>
-  </tr>
-  
-    <tr id="Assert-like-java-assert-null-analysis">
-    <td class="title">Null analysis treats org.eclipse.core.runtime.Assert like Java assert</td>
-    <td class="content">
-        Since <b>org.eclipse.core.runtime.Assert</b> is often used just like the Java <b>assert</b> keyword, JDT's null analysis considers
-		the boolean expression passed into the former as always true after the Assert reference, since if the condition did turn out to be false,
-		the control flow will never go further than the org.eclipse.core.runtime.Assert reference.
-		<p><img src="images/assert-warnings.png" alt="Code snippet showing the boolean expression passed into org.eclipse.core.runtime.Assert.isLegal(..) is considered true after the call"/></p>
-	</td>
-  </tr>
-  
-  <tr id="null-analysis-fields-withdrawn">
-    <td class="title">Null analysis for fields withdrawn</td>
-    <td class="content">
-		"No man loves the bearer of bad tidings", said Sophocles.
-       While we're proud to announce all the recent enhancements in JDT's null analysis, we have decided to withdraw the support added 
-	   for null analysis of fields in Juno M5 so that a more general and configurable solution could be considered in future without 
-	   being constrained by the present implementation.
-	   Stay tuned!
-	</td>
-  </tr>
-  
-  <tr id="resource-leak-default-warning">
-    <td class="title">Resource leak detection improved and enabled by default</td>
-    <td class="content">
-        Resource leak detection as introduced in JDT Juno M3 is now less aggressive if a resource
-		is shared between methods, possibly via a field, where any party accessing the resource
-		could possibly issue the desired call to close(). This, along with some fine tuning of the
-		analysis, results in a greatly reduced number of false positives. Thus, the detection of a
-		definite resource leak is now much more reliable and reporting is set to <b>warning</b> by default.
-		This can be configured in the <b>Java &gt; Compiler &gt; Errors/Warnings</b> preference page.
-		
-		<p><img src="images/resource-leak-default-warning.png" alt="Errors/Warnings page with 'Resource leaks' highlighted"/></p>
-	</td>
-  </tr>
-  
-  <tr id="incomplete-switch-over-enum">
-    <td class="title">Incomplete switch over enum</td>
-    <td class="content">
-        JDT now raises a new warning whenever a switch on an enum value lacks a default case, and the option 
-		<b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; Incomplete 'switch' cases over enum</b> is enabled.
-		<p><img src="images/switch-case-enum.png" alt="Warning on switch over enum with missing default case"/></p>
-		<p> Note that in cases like the above, the warning also helps to understand another
-		error against the last statement:<br/>
-		"The local variable printString may not have been initialized"
-		is reported because clients could possibly call the method <code>print(Color)</code> with an 
-		enum value that is not known at the time of compiling this method.</p>
-	</td>
-  </tr>
-  
-  <tr id="show-monitors-default">
-    <td class="title">Show Monitors on by default</td>
-    <td class="content">
-      The default setting for displaying monitor information in the <b>Debug</b> view is now set to <em>on</em>.
-      This change only affects new workspaces and does not change existing settings.
-      <p>
-      Showing monitor information can be turned on or off using the <b>Java &gt; Show Monitors</b> view action
-      within the <b>Debug</b> view.
-      </p>
-    </td>
-  </tr>
-  <tr id="toggle-bp-mod-keys">
-    <td class="title">Toggle breakpoint modifier keys</td>
-    <td class="content">
-      There is now support for modifier keys while toggling breakpoints in the Java editor:
-      <ul>
-        <li><p>Holding the <b>Ctrl</b> key while double-clicking (toggling) a breakpoint will cause the <b>Properties 
-        dialog</b> for that breakpoint to be displayed (on the Mac, use <b>Command</b>)</p>
-        </li>
-        <li>Holding the <b>Alt</b> key while double-clicking (toggling) a breakpoint will <b>enable / disable</b> that breakpoint</li>
-      </ul>
-      If there is no existing breakpoint, a normal breakpoint toggle takes place even if a modifier key is held down.
-    </td>
-  </tr>
-
-  <tr id="bracket-matching">
-	<td class="title">Improved bracket matching support in Java editor</td>
-	<td class="content">
-		The Java editor now supports highlighting of enclosing brackets.
-		<p><img src="images/enclosing-brackets.png" alt="Enclosing brackets"/></p>
-		
-		This can be configured on the <b>Java &gt; Editor</b> preference page.
-		<p><img src="images/bracket-highlighting-preferences.png" alt="Preferences for bracket highlighting"/></p>
-		
-		<p>Also, the <b>Navigate &gt; Go To &gt; Matching Bracket</b> action <b>(Ctrl+Shift+P)</b> now works everywhere in a file. If a bracket is not selected 
-		before invoking the action, the action navigates to the nearest enclosing end bracket. On invoking the action a second time, it
-		navigates to the corresponding start bracket. On the third invocation, the original selection is restored.</p>
-		
-		<p>Furthermore, the start bracket is now highlighted when the caret is before (not after) the end bracket.</p>  
-		<p><img src="images/matching-bracket.png" alt="Matching bracket example"/></p>
-	</td>
-  </tr>
-
-  <tr id="default-implementations-for-correction-proposals">
-	<td class="title">Default implementations for correction proposals</td>
-	<td class="content">
-		JDT now provides the following default implementations for correction proposals that can be used to contribute quick fixes and quick assists.
-		<ul>
-			<li><code>org.eclipse.jdt.ui.text.java.correction.ChangeCorrectionProposal</code></li>
-			<li><code>org.eclipse.jdt.ui.text.java.correction.CUCorrectionProposal</code></li>
-			<li><code>org.eclipse.jdt.ui.text.java.correction.ASTRewriteCorrectionProposal</code></li>
-		</ul>
-		This makes it easier to implement quick fixes/assists that operate on .java files and use an ASTRewrite.
-	</td>
-  </tr>
-  
-  <tr id="errors-warnings-highlight">
-    <td class="title">Highlighting on Errors/Warnings preference pages</td>
-    <td class="content">
-        On Errors/Warnings preference pages, it is sometimes hard to see which item is selected, especially
-        when you opened the dialog via the "Configure Problem Severity" button.
-        <p><img src="images/configure-problem-severity.png" alt="Configure Problem Severity button in Java Editor problem hover"/></p>
-        Now, an arrow highlights the selected item, and another arrow highlights the item under the mouse.
-        <p><img src="images/errors-warnings-highlight.png" alt="Highlighting in preference pages"/></p>
-        The highlighting also works on the PDE and API Tools preference pages.
-    </td>
-  </tr>
-  
-  
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  <tr id="target-configure-phase">
-    <td class="title">Target definition configure phase</td>
-    <td class="content">
-     When working with a target definition containing a software site location (such as a p2 repository) it is now possible to change whether the p2 configuration phase should be run when resolving the target.  By default the configuration phase is not included.  Changing the setting will change all locations in the target definition.
-     <p><img src="images/configurephase.png" alt="Configure phase option"/></p>
-    </td>
-  </tr>
-
-  <tr id="product-add-required">
-    <td class="title">Add required in feature based product</td>
-    <td class="content">
-     The product editor now has an <b>Add Required</b> button when editing a feature based product.  Pressing the button will add all the features that are required by the features already in the product configuration.
-     <p><img src="images/addrequired.png" alt="Add required button"/></p>
-    </td>
-  </tr>
-
-  <tr id="extensions-editor-enhancements">
-    <td class="title">Extension editor enhancements</td>
-    <td class="content">
-     Several improvements have been made to the extensions tab of the <b>Plug-in Editor</b>.
-     <p><img src="images/extensions2.png" alt="Extensions editor enhancements"/></p>  
-    <ul>
-      <li><b>Filter related:</b> Available by right clicking and pressing <b>Filter Related</b>, only extensions that are related (same id, label, class, etc) will be displayed in the tree</li>
-      <li><b>Filter enhancements:</b> The standard filter textbox now supports multiple filters separated by "/", matches are bolded, and the filter applies to extension attributes</li>
-      <li><b>Label improvements:</b> More items will display icons and labels, class names are displayed without package name</li>
-      <li><b>Accelerated scrolling:</b> Pressing <b>Ctrl</b> while scrolling does fast scrolling</li>
-      <li><b>Better expansion:</b> The expand state of selected items can be toggled with a new action</li>
-      <li><b>Search workspace:</b> Search the workspace for extensions related to items in the editor</li>
-    </ul>
-    </td>
-  </tr>
-
-  <tr id="workspace-deletion-cancel">
-    <td class="title">Workspace deletion is cancelable</td>
-    <td class="content">
-     Eclipse and OSGi launch configurations have the option to delete the workspace and configuration folders before launching.  This can be a long running operation with large workspaces.  The operation is now cancelable which will stop the launch.
-    </td>
-  </tr>
-
-  <tr id="api-tracing">
-    <td class="title">API Tools tracing</td>
-    <td class="content">
-     API Tools has added all debug tracing settings to the <b>Tracing</b> preference page where they can be enabled and disabled as needed without restarting.
-     <p><img src="images/tracing.png" alt="API Tools tracing"/></p>
-    </td>
-  </tr>
-
-  <tr id="ee-cleanup">
-    <td class="title">EE descriptions updated</td>
-    <td class="content">
-     The API Tools execution environment descriptions have been
-     updated with more accurate package information and have been renamed for easier installation.
-     To turn on warnings for invalid references to classes or methods that are not available in the configured execution environment, use the
-     <b>Plug-in Development &gt; API Errors/Warnings</b> preference page.
-     <p>The execution environment descriptions can be installed from the Eclipse update site
-     (<a href="http://download.eclipse.org/eclipse/updates/3.8-I-builds">http://download.eclipse.org/eclipse/updates/3.8-I-builds</a>)
-     under the <b>API Tools Execution Environment Descriptions</b> category.</p>
-     <p><img src="images/eedesc.png" alt="Updated EE descriptions"/></p>
-    </td>
-  </tr>
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Juno milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M5-201201271145/eclipse-news-M5.html">New for Eclipse Juno milestone build M5 (January 27, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M4-201112092100/eclipse-news-M4.html">New for Eclipse Juno milestone build M4 (December 9, 2011)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M3-201110281100/eclipse-news-M3.html">New for Eclipse Juno milestone build M3 (October 28, 2011)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M2-201109161615/eclipse-news-M2.html">New for Eclipse Juno milestone build M2 (September 16, 2011)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops/S-3.8M1-201108031800/eclipse-news-M1.html">New for Eclipse Juno milestone build M1 (August 5, 2011)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.2/M6/images/addrequired.png b/platform/4.2/M6/images/addrequired.png
deleted file mode 100644
index e6d04a8..0000000
--- a/platform/4.2/M6/images/addrequired.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/assert-warnings.png b/platform/4.2/M6/images/assert-warnings.png
deleted file mode 100644
index edc9a1e..0000000
--- a/platform/4.2/M6/images/assert-warnings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/bracket-highlighting-preferences.png b/platform/4.2/M6/images/bracket-highlighting-preferences.png
deleted file mode 100644
index 785f838..0000000
--- a/platform/4.2/M6/images/bracket-highlighting-preferences.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/configure-problem-severity.png b/platform/4.2/M6/images/configure-problem-severity.png
deleted file mode 100644
index 4084cb2..0000000
--- a/platform/4.2/M6/images/configure-problem-severity.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/configurephase.png b/platform/4.2/M6/images/configurephase.png
deleted file mode 100644
index 577145d..0000000
--- a/platform/4.2/M6/images/configurephase.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/custom-colors.png b/platform/4.2/M6/images/custom-colors.png
deleted file mode 100644
index 9869c03..0000000
--- a/platform/4.2/M6/images/custom-colors.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/eedesc.png b/platform/4.2/M6/images/eedesc.png
deleted file mode 100644
index 6de6cd7..0000000
--- a/platform/4.2/M6/images/eedesc.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/enclosing-brackets.png b/platform/4.2/M6/images/enclosing-brackets.png
deleted file mode 100644
index 707634e..0000000
--- a/platform/4.2/M6/images/enclosing-brackets.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/errors-warnings-highlight.png b/platform/4.2/M6/images/errors-warnings-highlight.png
deleted file mode 100644
index 751d0c2..0000000
--- a/platform/4.2/M6/images/errors-warnings-highlight.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/extensions2.png b/platform/4.2/M6/images/extensions2.png
deleted file mode 100644
index 89bd32d..0000000
--- a/platform/4.2/M6/images/extensions2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/ignore-warnings-source-folders.png b/platform/4.2/M6/images/ignore-warnings-source-folders.png
deleted file mode 100644
index 3b43113..0000000
--- a/platform/4.2/M6/images/ignore-warnings-source-folders.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/lcd-name-error.png b/platform/4.2/M6/images/lcd-name-error.png
deleted file mode 100644
index 62ab756..0000000
--- a/platform/4.2/M6/images/lcd-name-error.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/matching-bracket.png b/platform/4.2/M6/images/matching-bracket.png
deleted file mode 100644
index b4f379f..0000000
--- a/platform/4.2/M6/images/matching-bracket.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/missing-nonnullbydefault-option.png b/platform/4.2/M6/images/missing-nonnullbydefault-option.png
deleted file mode 100644
index c2c2f18..0000000
--- a/platform/4.2/M6/images/missing-nonnullbydefault-option.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/missing-nonnullbydefault-package.png b/platform/4.2/M6/images/missing-nonnullbydefault-package.png
deleted file mode 100644
index 30a121c..0000000
--- a/platform/4.2/M6/images/missing-nonnullbydefault-package.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/missing-nonnullbydefault-type.png b/platform/4.2/M6/images/missing-nonnullbydefault-type.png
deleted file mode 100644
index b42bfb6..0000000
--- a/platform/4.2/M6/images/missing-nonnullbydefault-type.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/monitorexpression_tsk.gif b/platform/4.2/M6/images/monitorexpression_tsk.gif
deleted file mode 100644
index 252d7eb..0000000
--- a/platform/4.2/M6/images/monitorexpression_tsk.gif
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/new-null-analysis-message1.png b/platform/4.2/M6/images/new-null-analysis-message1.png
deleted file mode 100644
index 69368c5..0000000
--- a/platform/4.2/M6/images/new-null-analysis-message1.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/new-null-analysis-message2.png b/platform/4.2/M6/images/new-null-analysis-message2.png
deleted file mode 100644
index 286f56d..0000000
--- a/platform/4.2/M6/images/new-null-analysis-message2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/new-null-analysis-message3.png b/platform/4.2/M6/images/new-null-analysis-message3.png
deleted file mode 100644
index 34d609a..0000000
--- a/platform/4.2/M6/images/new-null-analysis-message3.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/quick-outline-camel-case.png b/platform/4.2/M6/images/quick-outline-camel-case.png
deleted file mode 100644
index 602c182..0000000
--- a/platform/4.2/M6/images/quick-outline-camel-case.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/resource-leak-default-warning.png b/platform/4.2/M6/images/resource-leak-default-warning.png
deleted file mode 100644
index 3aa4a56..0000000
--- a/platform/4.2/M6/images/resource-leak-default-warning.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/switch-case-enum.png b/platform/4.2/M6/images/switch-case-enum.png
deleted file mode 100644
index ee098c0..0000000
--- a/platform/4.2/M6/images/switch-case-enum.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M6/images/tracing.png b/platform/4.2/M6/images/tracing.png
deleted file mode 100644
index af763fe..0000000
--- a/platform/4.2/M6/images/tracing.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/default_style.css b/platform/4.2/M7/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.2/M7/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.2/M7/eclipse-news-M7.html b/platform/4.2/M7/eclipse-news-M7.html
deleted file mode 100644
index a3cd949..0000000
--- a/platform/4.2/M7/eclipse-news-M7.html
+++ /dev/null
@@ -1,196 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse 3.8 and 4.2 M7 News</title>
-</head>
-<body>
-<h1>Eclipse 3.8 and 4.2 M7 - New and Noteworthy</h1>
-<p>The <a href="http://wiki.eclipse.org/Juno">Juno</a> annual release is almost upon us! Here are some of the 
-  more noteworthy things available in milestone build M7 
-  (May 4, 2012) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-Unless otherwise indicated, all entries listed here are available in both the 3.8 and 4.2 development streams.</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-
-  <tr id="new-icon">
-    <td class="title">New high resolution icon</td>
-    <td class="content">
-      The Eclipse SDK now has a shiny new icon. The icon is now in high resolution, making
-      for a much more polished appearance on modern operating systems.
-      <p><img src="images/icon.png" alt="New Eclipse icon"/></p>
-    </td>
-  </tr>
-
-  <tr id="lightweight-refresh">
-    <td class="title">Lightweight refresh enabled by default (4.2 only)</td>
-    <td class="content">
-      In Eclipse 3.7 a new lightweight refresh mechanism was introduced. Files discovered to be out-of-sync 
-      by the workspace, for example while accessing the file content by an editor, 
-      are automatically asynchronously refreshed. In Eclipse 3.7 and 3.8 you have to enable this yourself
-      via <b>Preferences > General > Workspace</b> and select <b>Refresh on access</b>.
-      In Eclipse SDK 4.2 the mechanism is enabled by default.
-      <p><img src="images/lightweight_refresh_by_default.png" alt="Lightweight refresh enabled by default"></p>
-    </td>
-  </tr>
-
-  <tr id="fullscreen">
-    <td class="title">Support for MacOS X Full Screen</td>
-    <td class="content">
-      A new <b>Window &gt; Toggle Full Screen</b> command is now supported on MacOS X Lion.
-    </td>
-  </tr>
-
-  <tr id="trim-dragging">
-    <td class="title">Trim dragging (4.2 only)</td>
-    <td class="content">
-	  We have finally re-introduced the ability to drag some of the window trim elements around. 
-	  For example, you can drag minimized stacks to different edges of the main window.
-      <p><img src="images/trim-dragging.png" alt="Trim dragging"/></p>
-    </td>
-  </tr>
-
-  <tr id="trim-styling">
-    <td class="title">Trim styling (4.2 only)</td>
-    <td class="content">
-      In the new window trim implementation, the drag handle and the frame surrounding the trim are 
-      defined through CSS. Here's an example of what this looks like:
-<pre>
-.MToolControl.TrimStack {
-	frame-image:  url(./winXPTSFrame.PNG);
-	handle-image:  url(./winXPHandle.PNG);
-	frame-cuts: 5px 1px 5px 16px;
-}
-</pre>
-	  <p><tt>frame-image</tt> and <tt>handle-image</tt> define the images to be used to draw the frame. 
-	  The <tt>frame-cuts</tt> attribute is a set of 4 integer values that are used to divide the <tt>frame-image</tt>
-	  into specific areas by defining two widths and two heights (the third is just the image size minus the 
-	  sum of the other two. This allows us to determine what part of the image to use for the top/right corner.</p>
-	  <p>Here is a more interesting example that illustrates the power this gives to applications to customize their appearance:</p>
-      <p><img src="images/trim-styling.png" alt="Trim styling"/></p> 
-    </td>
-  </tr>
-
-  <tr id="css-theme-event">
-    <td class="title">CSS-based Theme changed event (4.2 only)</td>
-    <td class="content">
-      An OSGi EventAdmin-based event is now raised on theme-change
-      (<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=369443">bug
-      369443</a>).
-    </td>
-  </tr>
-
-  <tr id="css-extension-points">
-    <td class="title">Changes to CSS Extension Points (4.2 only)</td>
-    <td class="content">
-      For those providing extensions for the new CSS support,
-      the extension points for providing property handlers and
-      element providers have been renamed to
-      <tt>org.eclipse.e4.ui.css.core.propertyHandler</tt> and
-      <tt>org.eclipse.e4.ui.css.core.elementProvider</tt>
-      (respectively).
-    </td>
-  </tr>
-
-  <tr id="ant-1-8-3">
-    <td class="title">Ant updated to 1.8.3</td>
-    <td class="content">
-      The bundled version of Apache Ant in the platform has been updated to version 1.8.3.
-      <p>For more information on what is new in Ant 1.8.3 please see the Apache Ant <a href="http://apache.claz.org//ant/README.html">release notes</a>.</p>
-    </td>
-  </tr>
-
-  <tr id="add-buildfiles-dialog">
-    <td class="title">Add all known buildfile types to Ant view</td>
-    <td class="content">
-      The <b>Buildfile Selection</b> dialog for the <b>Ant</b> view has been updated to allow filtering 
-      for all known kinds of build files rather than just <em>*.xml</em> and <em>build.xml</em>.
-      <p><img src="images/add-buildfiles.png" alt="The Add Buildfiles dialog"/></p> 
-    </td>
-  </tr>
-
-  <tr id="debug-tracing">
-    <td class="title">Debug tracing</td>
-    <td class="content">
-      JDT and Platform Debug have added all debug tracing settings to the <b>Tracing</b> preference page where they can be enabled and disabled as needed without restarting.
-      <p><img src="images/debug-trace.png" alt="Debug tracing options"/></p>
-    </td>
-  </tr>
-
-  <tr id="bp-view-sorting">
-    <td class="title">Breakpoint view sorting</td>
-    <td class="content">
-      The <b>Breakpoints</b> view now has improved sorting that will take into account any line 
-      numbers that appear in the label and sort accordingly.
-      <p><img src="images/bp-sorting.png" alt="Breakpoint view sorting"/></p>
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-
-  <tr id="content-assist-package-info">
-    <td class="title">Content assist in package-info.java</td>
-    <td class="content">
-      Content assist (<b>Ctrl+Space</b>) is now available inside package-info.java, which is used to declare package-level annotations and Javadocs.
-      <p><img src = "images/content-assist-pkg-info.png" alt = "Content assist popup to add package-level annotations on package declaration"/></p>
-    </td>
-  </tr>
-  <tr id="enhanced-switch-diagnostics">
-    <td class="title">Enhanced diagnostics for detection of incomplete switch statements</td>
-    <td class="content">
-      JDT now provides additional configurable diagnostics to flag an incomplete switch statement.
-      <p><img src = "images/switch-new-warnings.png" alt = "Compiler Errors/warnings preference page with new switch diagnostic options highlighted"/></p>
-	  <p> When you enable the option <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; Switch is missing default case</b>, JDT will flag switch statements with a missing default
-	      case, because such a switch statement can e.g. result in variables left uninitialized.</p>
-	  <p><img src="images/switch-missing-default.png" alt="Warning on switch with missing default case"/></p>
-	  <p> When you enable the sub-option <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; Signal even if default case exists</b> for the <b>Incomplete switch cases on enum</b> option, 
-	  JDT will flag switch statements over an enum type which may have an enum value covered only through a default statement, but not directly through a case
-	  statement. When new enum constants are added, this option will help in detecting the switch statements that do not cover the new value.</p>
-	  <p><img src="images/switch-missing-case-enum.png" alt="Warning on switch with missing case statement for enum value even though default is present"/></p>
-    </td>
-  </tr>
-  <tr id="bracket-matching">
-	<td class="title">Bracket matching improvements in Java editor</td>
-	<td class="content">
-		So far, a matching bracket was found when the caret was placed immediately after a bracket. Now,
-		a matching bracket is found both when the caret is placed either immediately before or immediately after a bracket.
-		<p><img src="images/matching-bracket.png" alt="Matching bracket examples"/></p>
-		
-		<p>You can hover over a closing curly brace and see the source near the matching opening brace in a hover. 
-		This is helpful when you want to see the code near the start of a long code block. The hover also tells the number of lines in the code block.</p> 
-		<p><img src="images/bracket-hover-1.png" alt="Bracket hover example 1"/></p>
-		<p>The hover is also useful to temporarily 'highlight' a short code block.</p>
-		<p><img src="images/bracket-hover-2.png" alt="Bracket hover example 2"/></p>
-	</td>
-  </tr>
-  
-  <tr id="junit-4-10">
-    <td class="title">JUnit 4.10</td>
-    <td class="content">
-      The JUnit 4 version shipped with Eclipse has been updated to <a href="https://github.com/KentBeck/junit/blob/r4.10/doc/ReleaseNotes4.10.txt">4.10</a>.
-    </td>
-  </tr>
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Juno milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M6-201203151300/eclipse-news-M6.html">New for Eclipse Juno milestone build M6 (March 16, 2011)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M5-201201271145/eclipse-news-M5.html">New for Eclipse Juno milestone build M5 (January 27, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M4-201112092100/eclipse-news-M4.html">New for Eclipse Juno milestone build M4 (December 9, 2011)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M3-201110281100/eclipse-news-M3.html">New for Eclipse Juno milestone build M3 (October 28, 2011)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.2M2-201109161615/eclipse-news-M2.html">New for Eclipse Juno milestone build M2 (September 16, 2011)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops/S-3.8M1-201108031800/eclipse-news-M1.html">New for Eclipse Juno milestone build M1 (August 5, 2011)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.2/M7/images/add-buildfiles.png b/platform/4.2/M7/images/add-buildfiles.png
deleted file mode 100644
index 8cefebd..0000000
--- a/platform/4.2/M7/images/add-buildfiles.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/bp-sorting.png b/platform/4.2/M7/images/bp-sorting.png
deleted file mode 100644
index c5502f2..0000000
--- a/platform/4.2/M7/images/bp-sorting.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/bracket-hover-1.png b/platform/4.2/M7/images/bracket-hover-1.png
deleted file mode 100644
index 19d1d45..0000000
--- a/platform/4.2/M7/images/bracket-hover-1.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/bracket-hover-2.png b/platform/4.2/M7/images/bracket-hover-2.png
deleted file mode 100644
index 3b5668b..0000000
--- a/platform/4.2/M7/images/bracket-hover-2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/content-assist-pkg-info.png b/platform/4.2/M7/images/content-assist-pkg-info.png
deleted file mode 100644
index e72b537..0000000
--- a/platform/4.2/M7/images/content-assist-pkg-info.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/debug-trace.png b/platform/4.2/M7/images/debug-trace.png
deleted file mode 100644
index a01d0c3..0000000
--- a/platform/4.2/M7/images/debug-trace.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/icon.png b/platform/4.2/M7/images/icon.png
deleted file mode 100644
index c07971b..0000000
--- a/platform/4.2/M7/images/icon.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/lightweight_refresh_by_default.png b/platform/4.2/M7/images/lightweight_refresh_by_default.png
deleted file mode 100644
index 17b1795..0000000
--- a/platform/4.2/M7/images/lightweight_refresh_by_default.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/matching-bracket.png b/platform/4.2/M7/images/matching-bracket.png
deleted file mode 100644
index 386ccd7..0000000
--- a/platform/4.2/M7/images/matching-bracket.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/switch-missing-case-enum.png b/platform/4.2/M7/images/switch-missing-case-enum.png
deleted file mode 100644
index 43a1799..0000000
--- a/platform/4.2/M7/images/switch-missing-case-enum.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/switch-missing-default.png b/platform/4.2/M7/images/switch-missing-default.png
deleted file mode 100644
index aac99c1..0000000
--- a/platform/4.2/M7/images/switch-missing-default.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/switch-new-warnings.png b/platform/4.2/M7/images/switch-new-warnings.png
deleted file mode 100644
index 967616b..0000000
--- a/platform/4.2/M7/images/switch-new-warnings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/trim-dragging.png b/platform/4.2/M7/images/trim-dragging.png
deleted file mode 100644
index 26f1379..0000000
--- a/platform/4.2/M7/images/trim-dragging.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/M7/images/trim-styling.png b/platform/4.2/M7/images/trim-styling.png
deleted file mode 100644
index 83e4cb4..0000000
--- a/platform/4.2/M7/images/trim-styling.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/MX/4.2MX-news.zip b/platform/4.2/MX/4.2MX-news.zip
deleted file mode 100644
index a58e8b4..0000000
--- a/platform/4.2/MX/4.2MX-news.zip
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/MX/default_style.css b/platform/4.2/MX/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.2/MX/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.2/MX/eclipse-news-MX.html b/platform/4.2/MX/eclipse-news-MX.html
deleted file mode 100644
index b67f9cf..0000000
--- a/platform/4.2/MX/eclipse-news-MX.html
+++ /dev/null
@@ -1,136 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse 3.8 and 4.2 MX News</title>
-</head>
-<body>
-<h1>Eclipse 3.8 and 4.2 MX - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build MX 
-  (Month dd, yyyy) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-Unless otherwise indicated, all entries listed here are available in both the 3.8 and 4.2 development streams.
-See the <a href="buildNotes.php">build notes</a> for details about bugs fixed and other changes.</p>
-<ul>
-  <li><a href="#Equinox">Equinox</a></li>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Equinox">Equinox</td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Resources</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">SWT</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Platform UI</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">User Assistance</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Platform Text</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Team/CVS</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Compare</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Ant</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Debug</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Template</div>
-      </td>
-  </tr>
-  <tr id="first-item">
-    <td class="title">First item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Juno milestone builds:</p>
-<ul>
-  <li>New for Eclipse Juno milestone build M7 (April 27, 2011)</li>
-  <li>New for Eclipse Juno milestone build M6 (March 16, 2011)</li>
-  <li>New for Eclipse Juno milestone build M5 (January 27, 2011)</li>
-  <li>New for Eclipse Juno milestone build M4 (December 9, 2010)</li>
-  <li>New for Eclipse Juno milestone build M3 (October 28, 2010)</li>
-  <li>New for Eclipse Juno milestone build M2 (September 16, 2010)</li>
-  <li>New for Eclipse Juno milestone build M1 (August 5, 2010)</li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.2/final/default_style.css b/platform/4.2/final/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.2/final/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.2/final/eclipse-news-part1.html b/platform/4.2/final/eclipse-news-part1.html
deleted file mode 100644
index 3f98858..0000000
--- a/platform/4.2/final/eclipse-news-part1.html
+++ /dev/null
@@ -1,318 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2012. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Juno - New and Noteworthy</title>
-</head>
-<body>
-<h2>Platform and Equinox</h2>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table class="news" cellpadding="10" cellspacing="0">
-
-  <!-- ******************** Platform ********************** -->
-  <tr>
-    <td id="Platform" class="section" colspan="2"><h2>Platform Changes</h2></td>
-  </tr>
-
-  <tr id="new-look">
-    <td class="title">New look for the workbench</td>
-    <td class="content">
-    The default appearance of the platform user interface has been refreshed. The main
-    goals of this update were to adopt a more modern visual style, reduce clutter, and
-    use whitespace rather than extra keylines to separate user interface elements. Tabs
-    and part stacks have been redesigned to reduce emphasis on non-selected tabs and stacks.
-    <p><img src="images/newlook.png" width="700" alt="Screenshot of workbench with new default presentation" /></p></td>
-  </tr>
-
-  <tr id="search-bar">
-    <td class="title">Global search bar</td>
-    <td class="content">
-    The workbench now has a global search field in the tool bar. This provides a visible
-    affordance for the "Quick Access" feature, and may be used in the future to 
-    combine other kinds of searches into a single location.
-    <p><img src="images/searchbar.png" alt="Screenshot of workbench highlighting search bar" /></p></td>
-  </tr>
-
-  <tr id="flexible-part-layout">
-    <td class="title">More flexible part layout</td>
-    <td class="content">
-    You can now stack views and editors together by default. For example a view
-    that requires a large working area can be stacked in the editor area to provide more space.
-    <p><img src="images/mixvieweditor.png" alt="Screenshot of views and editors in editor area" /></p>
-    <p>Not only can you mix views and editors, but you can split the editor area to put a view 
-    beside an editor in the editor area, and then maximize the entire editor area to work with both at the same time.</p>
-    <p><img src="images/splitvieweditor.png" width="700" alt="Screenshot of views and editors in editor area" /></p>
-    </td>
-  </tr>
-
-  <tr id="editor-area-container">
-    <td class="title">Editor area</td>
-    <td class="content">A specialized container has been introduced to allow
-    the UI to properly represent the editor area. This affordance lets the user know that this
-    area behaves differently - for example the entire area can be maximized, and all views and
-    editors within the area will be affected.
-	<p>
-	You will not see any 'area' indication if there is only a single stack there. If there is more 
-	than one stack in the shared area, you see the area's boundary, with a 'fly out' hover area
-	that will show the minimize/maximize buttons.
-	</p>
-	<p>	<img src="images/shared-area-polish.png" alt="Editor Area"/></p>
-    </td>
-  </tr>
-
-  <tr id="detached-editors">
-    <td class="title">Detached editors</td>
-    <td class="content">
-      Editors can now be detached into their own windows. The detached 
-      editor will not be treated any differently from an editor
-      contained within the workbench window. This resolves 
-      <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=8886">bug 8886</a>,
-      one of the platform's oldest and most voted for enhancements.
-      <p><img src="images/detached-editor.png" alt="An editor detached from Eclipse's main workbench window."/></p>
-    </td>
-  </tr>
-
-  <tr id="multi-drag-sash">
-    <td class="title">Multi-drag sash</td>
-    <td class="content">
-	You can now place the cursor at the intersection of two or more sashes and
-	drag them all at the same time. When you are going to be dragging multiple sashes, the cursor
-	will change to one with 4-way arrows. The image below indicates one such
-	intersection with a red circle.
-	<p>	<img src="images/drag-sash.png" alt="Drag Sash"/></p>
-    </td>
-  </tr>
-
-  <tr id="platform-fade-effects">
-    <td class="title">Fade transition on maximize</td>
-    <td class="content">
-	A 'fade' effect has been added to the maximize / restore operation. You can turn the fade 
-	effect off using the animations preference, found under <b>Window &gt; Preferences &gt; General &gt; Appearance</b>
-	(see a <a href="http://www.youtube.com/watch?v=07kESXY5m2Q" target="_blank">video</a>).
-	</td>
-  </tr>
-
-  <tr id="new-icon">
-    <td class="title">New high resolution icon</td>
-    <td class="content">
-      The Eclipse SDK now has a shiny new icon. The icon is now in high resolution, making
-      for a much more polished appearance on modern operating systems.
-      <p><img src="images/icon.png" alt="New Eclipse icon"/></p>
-    </td>
-  </tr>
-
-  <tr id="open-resource-show-in">
-    <td class="title">Open Resource dialog supports Show In</td>
-    <td class="content">
-      The Open Resource dialog (<b>Ctrl+Shift+R</b>) has a new <b>Show In &gt; ...</b> context menu item that
-      allows to show selected resources in a view instead of opening them in an editor.
-      <p>
-          <img src="images/open-resource-show-in.png" alt=""/>
-      </p>
-    </td>
-  </tr>
-
-  <tr id="Platform-delete-project">
-    <td class="title">Delete project dialog shows project location</td>
-    <td class="content">
-      The Delete Resources dialog now shows the location of projects to be deleted on the file system:
-      <p>
-          <img src="images/delete-project.png" alt="Projects to be deleted"/>
-      </p>
-    </td>
-  </tr>
-
-  <tr id="swt-vo-context-menu">
-      <td class="title">VoiceOver context menu</td>
-      <td class="content">
-      On the Mac, you can now use the keyboard to open a context menu when VoiceOver is running,
-      using the standard VoiceOver key sequence Control+Option+Shift+M.
-      </td>
-    </tr>
-
-  <tr id="context-menu-shortcut">
-    <td class="title">Shortcut for context menu on the Mac</td>
-    <td class="content">
-      <b>Shift+F10</b> now also opens the context menu on the Mac, like it already worked on most other platforms.
-      The key binding of the new <b>Show Context Menu</b> command can be configured on the <b>General &gt; Keys</b> preference page.
-      <p><img src="images/context-menu.png" alt="Screenshot of a context menu in the Synchronize view"/></p>
-    </td>
-  </tr>
-
-  <tr id="screenshots">
-    <td class="title">Editor area tab navigation</td>
-    <td class="content">
-        Navigation arrows have been introduced to the sides of the editor area to allow
-        you to click and view the tabs that are to the left and right of the currently
-        selected tab. This is the default setting on new installations. Switching to the
-        Classic theme from the preferences (<b>Preferences &gt; General &gt; Appearance</b>)
-        will allow you to bring back the MRU behaviour from 3.x. The MRU behaviour can
-        also be toggled on and off via CSS by setting the <code>mru-visible</code> attribute
-        of an <code>MPartStack</code> to <code>true</code> or <code>false</code>.
-      <p>
-        <img src="images/tab-navigation.png" alt="The shared area with left and right navigation arrows on its sides."/>
-      </p>
-    </td>
-  </tr>
-
-  <tr id="lightweight-refresh">
-    <td class="title">Lightweight refresh enabled by default</td>
-    <td class="content">
-      In Eclipse 3.7 a new lightweight refresh mechanism was introduced. Files discovered to be out-of-sync 
-      by the workspace, for example while accessing the file content by an editor, 
-      are automatically asynchronously refreshed. In Eclipse 3.7 and 3.8 you have to enable this yourself
-      via <b>Preferences > General > Workspace</b> and select <b>Refresh on access</b>.
-      In Eclipse SDK 4.2 the mechanism is enabled by default.
-      <p><img src="images/lightweight_refresh_by_default.png" alt="Lightweight refresh enabled by default"/></p>
-    </td>
-  </tr>
-
-  <tr id="fullscreen">
-    <td class="title">Support for MacOS X Full Screen</td>
-    <td class="content">
-      A new <b>Window &gt; Toggle Full Screen</b> command is now supported on MacOS X Lion.
-    </td>
-  </tr>
-
-  <tr id="ant-1-8-3">
-    <td class="title">Ant updated to 1.8.3</td>
-    <td class="content">
-      The bundled version of Apache Ant in the platform has been updated to version 1.8.3.
-      <p>For more information on what is new in Ant 1.8.3 please see the Apache Ant <a href="http://apache.claz.org//ant/README.html">release notes</a>.</p>
-    </td>
-  </tr>
-
-  <tr id="ant-editor-extension-point">
-    <td class="title">Enhanced Editor Support for Ant 1.8.2</td>
-    <td class="content">
-      The Ant editor has been enhanced with support for the new <a href="http://ant.apache.org/manual/targets.html#extension-points">extension-point</a> 
-      features in Ant 1.8.2.
-      <p><img src="images/ant-extension-assist.png" alt="Ant extension point editor content assist"/></p>
-    </td>
-  </tr>
-
-  <tr id="add-buildfiles-dialog">
-    <td class="title">Add all known buildfile types to Ant view</td>
-    <td class="content">
-      The <b>Buildfile Selection</b> dialog for the <b>Ant</b> view has been updated to allow filtering 
-      for all known kinds of build files rather than just <em>*.xml</em> and <em>build.xml</em>.
-      <p><img src="images/add-buildfiles.png" alt="The Add Buildfiles dialog"/></p> 
-    </td>
-  </tr>
-
-  <!-- ******************** Text ********************** -->
-  <tr>
-    <td id="Text" class="section" colspan="2"><h2>Editor Changes</h2></td>
-  </tr>
-
-  <tr id="Platform-use-saturated-colors">
-    <td class="title">Use saturated colors in overview ruler</td>
-    <td class="content">
-      The new <b>Use saturated colors in overview ruler</b> preference allows to show the annotations in the Overview ruler using saturated colors:
-      <p>
-          <img src="images/use-saturated-colors-on.png" alt="Screenshot with saturated colors" title="saturated colors"/>
-          &nbsp;
-          <img src="images/use-saturated-colors-off.png" alt="Screenshot without saturated colors" title="lighter colors"/>
-          &nbsp;
-          <img src="images/use-saturated-colors.png" alt="Screenshot of the 'Accessibility' preference page"/>
-      </p>
-      <p>
-        This option is turned off by default and can be enabled on the <b>General &gt; Editors &gt; Text Editors &gt; Accessibility</b>
-        page.
-      </p>
-    </td>
-  </tr>
-
-  <!-- ******************* Team/CVS ******************** -->
-  <tr>
-    <td id="TeamCVS" class="section" colspan="2"><h2>Team/CVS Changes</h2></td>
-  </tr>
-
-  <tr id="cvs-sync-filters">
-    <td class="title">Filters in CVS Sync View</td>
-    <td class="content">
-      You can now use regular expressions to filter out changes in the CVS <b>Synchronize</b> view. 
-      To enable filters go to <b>Preferences > General > Team > CVS > Synchronize/Compare</b>, 
-      uncheck <b>Only look at timestamps to detect changes</b> and enter your regex pattern 
-      in the <b>Regular expression to ignore changes in synchronizations</b> field. Each difference 
-      in a change is checked against the pattern and is considered as matched, if either left or right side 
-      of the difference matches. If all diffs in a file match, the file is excluded from the view.
-      <p>
-        <img src="images/filters-in-cvs-syncview.png" alt="Preferences for filters in CVS Sync View "/>
-      </p>
-    </td>
-  </tr>
-
-  <!-- ******************** Debug ********************* -->
-  <tr>
-    <td id="Debug" class="section" colspan="2"><h2>Debug Changes</h2></td>
-  </tr>
-
-  <tr id="Platform-debug-toolbar">
-    <td class="title">Global debug toolbar</td>
-    <td class="content">To improve the presentation of the Debug perspective, the common debug control commands 
-    (Stop, Resume, etc.) have been moved out of the <b>Debug</b> view and into the global toolbar.  
-	<p><img src="images/debug_toolbar-1.png" alt="Global debug toolbar"/></p>
-    <p>
-    The global toolbar can be customized with the <b>Window &gt; Customize Perspective...</b> action to add or 
-    remove debugging commands, or to show/hide the debug toolbar completely. 
-    </p>
-    <p>
-    Old toolbar behavior can be restored by first toggling the <b>Show Debug Toolbar</b> option in the <b>Debug</b> 
-    view's menu, then by disabling the Debug toolbar from the <b>Customize Perspective</b> dialog.</p>
-	<p><img src="images/debug_toolbar-2.png" alt="Debug view toolbar action"/></p>
-    </td>
-  </tr>
-
-  <tr id="edit-multi-line-vars">
-    <td class="title">Improved editing of environment variables</td>
-    <td class="content">
-        Editing multi-line environment variables is now much simpler with a new UI that presents the variables in a scrolling text widget.
-        The new UI can be found in the edit dialog for a multi-line environment variable on the <b>Environment</b> tab of a supporting launch configuration.
-        <p><img src="images/multi-env-var.png" alt="New edit dialog for multi-line environment variables"/></p>
-    </td>
-  </tr>
-
-  <tr id="launch-config-name-validation">
-    <td class="title">Improved launch configuration name validation</td>
-    <td class="content">
-    Now if you create a launch configuration with the name of an existing configuration, the type of the conflicting configuration
-    is noted in the error message.
-    <p><img src="images/lcd-name-error.png" alt="Launch configuration dialog showing name conflict error"/></p>
-    </td>
-  </tr>
-
-  <tr id="debug-tracing">
-    <td class="title">Debug tracing</td>
-    <td class="content">
-      JDT and Platform Debug have added all debug tracing settings to the <b>Tracing</b> preference page where they can be enabled and disabled as needed without restarting.
-      <p><img src="images/debug-trace.png" alt="Debug tracing options"/></p>
-    </td>
-  </tr>
-
-  <tr id="bp-view-sorting">
-    <td class="title">Breakpoint view sorting</td>
-    <td class="content">
-      The <b>Breakpoints</b> view now has improved sorting that will take into account any line 
-      numbers that appear in the label and sort accordingly.
-      <p><img src="images/bp-sorting.png" alt="Breakpoint view sorting"/></p>
-    </td>
-  </tr>
-
-  <!-- ****************** END OF N&N TABLE ****************** -->
-</table>
-
-<p align="center"><font color="#808080">Previous</font>&nbsp;&nbsp;&nbsp;&nbsp; <a href="eclipse-news-part2.html">Next</a></p>
-</body>
-</html>
diff --git a/platform/4.2/final/eclipse-news-part2.html b/platform/4.2/final/eclipse-news-part2.html
deleted file mode 100644
index aa92c82..0000000
--- a/platform/4.2/final/eclipse-news-part2.html
+++ /dev/null
@@ -1,458 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2012. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Juno - New and Noteworthy</title>
-</head>
-<body>
-<h2>Java development tools</h2>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-
-<table class="news" cellpadding="10" cellspacing="0">
-
-  <tbody>
-  
-  <!-- ******************* Java Editor ************************************* -->
-  <tr>
-    <td id="JavaEditor" class="section" colspan="2">
-    <h2>Java Editor </h2>
-    </td>
-  </tr>
-
-  <tr id="quick-outline-camel-case">
-    <td class="title">CamelCase in Quick Outline</td>
-    <td class="content">
-        The <b>Quick Outline (Ctrl+O)</b> and <b>Quick Hierarchy (Ctrl+T)</b> in the Java Editor now also
-        support camelCase matching on the element name, quite similar to the Open Type dialog and Content Assist.
-		<p><img src="images/quick-outline-camel-case.png" alt="Quick Outline of StyledText with pattern 'gCa'"/></p>
-		The * and ? wildcards still work, of course.
-    </td>
-  </tr>
-
-  <tr id="jdt-convert-enhanced-for-loop">
-    <td class="title">Quick Assist to convert enhanced <code>for</code> loop</td>
-    <td class="content">
-      Ever encountered an enhanced <code>for</code> loop and needed access to the <code>Iterator</code> or to the loop index?
-      Now, you can just use a Quick Assist (<b>Ctrl+1</b>) to convert the loop:
-      <p>
-          <img src="images/convert-to-for-loop.png" alt="Screenshot of Quick Assist on the 'for' keyword of an enhanced 'for' loop"/>
-      </p>
-      <ul>
-        <li><b>Convert to indexed 'for' loop</b> is available for expressions of array- and <code>List</code>-based types.</li>
-        <li><b>Convert to Iterator-based 'for' loop</b> is available for expressions of type <code>Iterable</code>.</li>
-      </ul>
-    </td>
-  </tr>
-
-  <tr id="bracket-matching">
-	<td class="title">Improved bracket matching support in Java editor</td>
-	<td class="content">
-		The Java editor now supports highlighting of enclosing brackets.
-		<p><img src="images/enclosing-brackets.png" alt="Enclosing brackets"/></p>
-		
-		This can be configured on the <b>Java &gt; Editor</b> preference page.
-		<p><img src="images/bracket-highlighting-preferences.png" alt="Preferences for bracket highlighting"/></p>
-		
-		<p>Also, the <b>Navigate &gt; Go To &gt; Matching Bracket</b> action <b>(Ctrl+Shift+P)</b> now works everywhere in a file. If a bracket is not selected 
-		before invoking the action, the action navigates to the nearest enclosing end bracket. On invoking the action a second time, it
-		navigates to the corresponding start bracket. On the third invocation, the original selection is restored.</p>
-		
-		<p>So far, a matching bracket was found when the caret was placed immediately after a bracket. Now,
-		a matching bracket is found both when the caret is placed either immediately before or immediately after a bracket.</p>
-		<p><img src="images/matching-bracket.png" alt="Matching bracket examples"/></p>
-		
-		<p>You can hover over a closing curly brace and see the source near the matching opening brace in a hover. 
-		This is helpful when you want to see the code near the start of a long code block. The hover also tells the number of lines in the code block.</p> 
-		<p><img src="images/bracket-hover-1.png" alt="Bracket hover example 1"/></p>
-		<p>The hover is also useful to temporarily 'highlight' a short code block.</p>
-		<p><img src="images/bracket-hover-2.png" alt="Bracket hover example 2"/></p>
-	</td>
-  </tr>
-
-  <tr id="javadoc-hover-parameter-annotations">
-    <td class="title">Javadoc hover shows parameter annotations</td>
-    <td class="content">
-        Javadoc hovers now render the annotations on method parameters:
-        <p><img src="images/javadoc-hover-parameter-annotations.png" alt="org.eclipse.User.User(@NonNull String name, int uid, @Nullable String email)"/></p>
-    </td>
-  </tr>
-
-  <tr id="JDT-editor-for-class-without-source">
-    <td class="title">'*.class without source' file type</td>
-    <td class="content">
-      The new <b>*.class without source</b> file type allows to associate an internal or external editor
-      to class files that have no source attached. This e.g. allows to open the class file in a decompiler:
-      <p>
-          <img src="images/file-associations-page.png" alt="Screenshot of the 'File Associations' preference page"/>
-      </p>
-    </td>
-  </tr>
-
-  <tr id="default-implementations-for-correction-proposals">
-	<td class="title">Default im&shy;ple&shy;men&shy;ta&shy;tions for correction proposals</td>
-	<td class="content">
-		JDT now provides the following default implementations for correction proposals that can be used to contribute quick fixes and quick assists.
-		<ul>
-			<li><code>org.eclipse.jdt.ui.text.java.correction.ChangeCorrectionProposal</code></li>
-			<li><code>org.eclipse.jdt.ui.text.java.correction.CUCorrectionProposal</code></li>
-			<li><code>org.eclipse.jdt.ui.text.java.correction.ASTRewriteCorrectionProposal</code></li>
-		</ul>
-		This makes it easier to implement quick fixes/assists that operate on .java files and use an ASTRewrite.
-	</td>
-  </tr>
-
-  <tr id="content-assist-package-info">
-    <td class="title">Content assist in package-info.java</td>
-    <td class="content">
-      Content assist (<b>Ctrl+Space</b>) is now available inside package-info.java, which is used to declare package-level annotations and Javadocs.
-      <p><img src = "images/content-assist-pkg-info.png" alt = "Content assist popup to add package-level annotations on package declaration"/></p>
-    </td>
-  </tr>
-
-  <!-- ******************* Java Compiler ************************************* -->
-  <tr>
-    <td id="JavaCompiler" class="section" colspan="2">
-    <h2>Java Compiler</h2>
-    </td>
-  </tr>
-
-  <tr id="ignore-warnings-source-folders">
-    <td class="title">Selectively ignore errors/warnings from source folders</td>
-    <td class="content">
-        You can now configure JDT to ignore optional errors/warnings from certain source folders. 
-		<b>Project properties &gt; Java Build Path &gt; Compiler &gt; Source</b>.
-		<p><img src="images/ignore-warnings-source-folders.png" alt="Java Build path page with 'Ignore optional compile problems' highlighted"/></p>
-        <p>
-		With this option set to <b>Yes</b>, JDT will suppress errors/warnings configured in the 
-		<b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings</b> page. This can be desirable
-		for source folders that contain auto-generated classes or tests.
-      </p>
-    </td>
-  </tr>
-
-  <tr id="enhanced-switch-diagnostics">
-    <td class="title">Enhanced diagnostics for detection of incomplete switch statements</td>
-    <td class="content">
-      	The JDT's analysis regarding incomplete switch statements is now stronger and can be configured more in detail.
-	  	<p>The compiler now separately checks two criteria for a switch statement to be complete:</p>
-	  	<ul>
-	  	<li>A switch statement on an enum should define one case statement for each of the enum's constants</li>
-	  	<li>Each switch statement independent of type should define a default case.</li>
-	  	</ul>
-	  	<p>By default the compiler warns for an enum switch where both criteria are violated:</p>
-      	<p><img src="images/switch-case-enum.png" alt="Warning on switch over enum with missing default case"/></p>
-	  	<p>This warning is controlled by the option <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; Incomplete 'switch' cases on enum</b>.
-	  	  This option can be strengthened by selecting the new sub-option <b>Signal even if 'default' case exists</b>,
-	  	  in which case JDT will flag switch statements over an enum type which may have an enum value covered only through a default statement, but not directly through
-	  	  a case statement. When new enum constants are added, this option will help in detecting the switch statements that do not cover the new value.</p>
-	  	<p><img src="images/switch-missing-case-enum.png" alt="Warning on switch with missing case statement for enum value even though default is present"/></p>
-      	<p><img src = "images/switch-new-warnings.png" alt = "Compiler Errors/warnings preference page with new switch diagnostic options highlighted"/></p>
-	  	<p> A second addition in the same section of the compiler preferences, <b>Switch is missing 'default' case</b>, controls whether the JDT will flag switch statements 
-	  	  with a missing default case, because such a switch statement will be skipped entirely at runtime if an unexpected value occurs.</p>
-		<p><img src="images/switch-missing-default.png" alt="Warning on switch with missing default case"/></p>
-		<p> Note that in cases like the above, the warning also helps to understand another
-		error against the last statement:<br/>
-		"The local variable printString may not have been initialized"
-		is reported because clients could possibly call the method <code>print(Color)</code> with an 
-		enum value that is not known at the time of compiling this method.</p>
-    </td>
-  </tr>
-
-  <tr id="JDT-resource-leaks">
-    <td class="title">New options to detect resource leaks</td>
-    <td class="content">The compiler can now detect leakage of resources i.e. local variables of type
-      <code>java.lang.AutoCloseable</code> (compliance &gt;= 1.7) and <code>java.io.Closeable</code> (compliance &lt;= 1.6).
-	  <p><img src="images/resource-leak-default-warning.png" alt="Errors/Warnings page with 'Resource leaks' highlighted"/></p>
-      <p> When the <b>Resource leak</b> option on the <b>Java &gt; Compiler &gt; Errors/Warnings</b> preference page is enabled,
-      the compiler will issue an error or a warning if the <code>close()</code> method is not invoked locally on a resource.</p>
-      <p>
-       <img src="images/resource-leak-example.png"
-          alt="Resource leak example"
-          title="Compiler warning on an unclosed resource"/>
-      </p>
-
-      <p> When you enable the <b>Potential resource leak</b> option on the <b>Java &gt; Compiler &gt; Errors/Warnings</b> preference page,
-      the compiler will issue an error or a warning if the <code>close()</code> method is not invoked locally on a resource
-      on all the execution paths.</p>
-      <p>
-       <img src="images/pot-resource-leak-example.png"
-          alt="Potential resource leak example"
-          title="Compiler warning on a resource not closed on all execution paths"/>
-      </p>
-      <p> This analysis is less aggressive if a resource is <em>shared between methods</em>, possibly via a field, 
-        where any party accessing the resource could possibly issue the desired call to close().
-        In some cases (e.g.: passed as an argument to another method) the warning will be softened
-        to only report a <em>potential</em> leak, in other cases (stored in a field) the analysis
-        will be entirely silent.
-	  </p>
-	  <p> Additionally the analysis recognizes certain cases as being <em>practically unimportant</em>. 
-	  	Some examples where the absence of a close() call does not trigger any error/warning are given below:
-	  </p>
-		<ul>
-		<li> Resource-less implementors of Closeable, such as StringReader.
-		<p><img src="images/os-less-unclosed-resource.png" alt="no resource leak reported if resource-less implentor of Closeable is not closed"/></p>
-		</li>
-		<li> Wrapping implementors of Closeable, such as BufferedReader, that simply wrap a resource-less Closeable, directly or indirectly.
-		<p><img src="images/wrapped-os-less-unclosed-resource.png" alt="no resource leak reported when a resource which wraps a resource-less implentor of Closeable is not closed"/></p>
-		</li>
-		<li> Wrapped resources where any resource in the chain is (potentially) closed.
-		<p><img src="images/wrapped-resource.png" alt="potential resource leak reported when any resource in the chain of wrapper resources is closed along some execution path."/></p>
-		</li>
-		</ul>
-      </td>
-    </tr>
-
-  <tr id="JDT-batch-compiler">
-    <td class="title">New Batch compiler warning options</td>
-
-    <td class="content">Two new batch compiler options are now available to configure the
-      compile time warnings:
-      <ul>
-        <li><b>-warn:all</b> can be used to enable all compiler warnings</li>
-        <li><b>-warn:resource</b> can be used to enable resource leak warnings</li>
-      </ul>
-      </td></tr>
-      <tr id="JDT-build-path">
-    <td class="title">New build path option to warn when a source folder's output location overlaps another source folder</td>
-
-    <td class="content">JDT now shows a build path error when a source folder's output location overlaps another source folder.
-       This error can be configured on the <b>Java &gt; Compiler &gt; Building &gt; Output location overlaps source location</b> preference page.
-       <p>
-       <img src="images/buildpath-error.png"
-          alt="Build path error when source folder's output location overlaps another source folder"
-          title="Build path error because src2's output location is src"/></p>
-    </td>
-  </tr>
-
-  <tr id="annotation-null-analysis">
-    <td class="title">Annotation-based null analysis</td>
-    <td class="content">
-        JDT can now be configured to use annotations designated as null annotations to 
-		perform enhanced inter-procedural null analysis. This feature can be enabled in
-		
-		<b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; Null analysis</b>:
-		<p><img src="images/null-prefs.png" alt="Errors/Warnings preference page with 'Enable annotation-based null analysis' highlighted"/></p>
-		
-		<p> You can use either the default annotations bundled with JDT or use your own annotations
-		as null annotations. In addition to enabling the null analysis, the annotations need to be on the 
-		Java build path of your project. The default annotations can be found in the <b>org.eclipse.jdt.annotation</b> JAR
-		in the <code>plugins</code> directory, which can be consumed as an OSGi bundle or plain JAR.</p>
-		<p>When annotation-based null analysis is enabled, JDT issues new diagnostics based on the nullness
-			of a variable or a method return type as specified by a null annotation.</p>
-		
-		<p><img src="images/null-annotation-problems1.png" alt="	public void foo(@NonNull Object o1) {&para;		System.out.println(o1.toString()); // OK: o1 cannot be null&para;	}&para;	&para;	@NonNull Object bar(@Nullable String s1) {&para;		foo(null); // cannot pass null argument&para;		@NonNull String s= null; // cannot assign null value &para;		@NonNull String t= s1; // cannot assign potentially null value &para;		return null; // cannot return null value&para;	}"/></p>
-		<p> Similar diagnostics are also elicited when the value assigned/returned may potentially be null or has unknown nullness.</p>
-		
-		<p> Overriding methods are also checked for correctness:</p>
-		<p><img src="images/null-annotation-problems2.png" alt="class Base {&para;	@NonNull Object method(@Nullable Object o) {&para;		return new Object();&para;	}&para;}&para;&para;class Sub extends Base {&para;	@Override            // method parameter must allow null&para;	@Nullable Object method(@NonNull Object o) {&para;		return new Object();&para;	}&para;}"/></p>
-
-		<p> You can also use the <code>@NonNullByDefault</code> annotation to set a global default on an element (package, type, method) for all enclosed elements.</p>
-		<p><img src="images/null-annotation-problems-redundant1.png" alt="@NonNullByDefault&para;class MyClass {&para;	// redundant @NonNull annotations:&para;	public @NonNull Object foo(@NonNull Object o) {&para;		return o;&para;	}&para;	&para;	@NonNullByDefault(false) // cancels the default&para;	Object bar(@NonNull Object o) {&para;		return o;&para;	}&para;}"/></p>
-
-		<p> As a result of annotating method signatures, the existing intra-procedural null analysis has even more information
-		because of user-specified annotations and thus provides better results. In the example below, the compiler would not have
-		been able to evaluate the null status of parameter 'obj' without the null annotation 
-		(option <b>Redundant null check</b> must be enabled to see the warning).</p>
-		<p><img src="images/null-annotation-problems-redundant2.png" alt="public void foo(@NonNull Object obj) {&para;		if (obj == null) { }&para;	}"/></p>
-		
-		<p>The new diagnostics are classified in three categories:</p>
-		<ul>
-		<li><b>Violation of null specification</b><br/>
-			<img src="images/new-null-analysis-message1.png" alt="This option produces the&para;			'Null type mismatch: required '@NonNull String' but the provided value is specified as @Nullable' warning"/>
-			<p>Here, 'in' is not a legal return value because of the @Nullable annotation in its <b>declaration</b>.</p>
-		</li>
-		<li><b>Conflict between null annotations and null inference</b><br/>
-			<img src="images/new-null-analysis-message2.png" alt="This option produces the&para;			'Null type mismatch: required @NonNull String but the provided value is inferred as @Nullable' warning"/>
-			<p>Here, 'local' is not a legal return value, because flow analysis for the un-annotated variable 'local' <b>infers</b> that 
-			it can be null on some path.</p>
-		</li>
-		<li><b>Unchecked conversion from non-annotated type to @NonNull type</b><br/>
-			<img src="images/new-null-analysis-message3.png" alt="This option produces the&para;			'Null type safety: The expression of type String needs unchecked conversion to conform to @NonNull String' warning"/>
-			<p>Here, the return value from 'getLegacyValue()' may or may not be compatible to '@NonNull String'. 
-			Similar to converting a legacy raw type to a generic type, also here essential type information is missing 
-			since 'getLegacyValue()' has no @NonNull or @Nullable annotation.</p>
-		</li>
-		</ul>
-		<p><b>Note:</b> This is the first version of this feature. We are working on making this
-		easier to consume in Java project setups.
-		The implemented features are complete and tested, but e.g. support for annotating fields or
-		APIs from third-party libraries is currently missing.
-		An initial set of quick fixes is included which will be further improved in the future.
-		</p>
-    </td>
-  </tr>
-
-  <tr id="batch-compiler-null-annotations">
-    <td class="title">Batch compiler options for using null annotations</td>
-    <td class="content">
-        You can now configure the batch compiler to use annotations for null analysis by passing the token <b>nullAnnot(nullable|nonnull|nonnullbydefault)</b> to the <code>-warn</code> option, 
-		where nullable, nonnull and nonnullbydefault are the fully qualified names of the annotation types to be used for null analysis. You can use <b>nullAnnot</b> alone
-		to use JDT's default annotations.
-		<p>In addition, you can use the <b>-nonNullByDefault</b> token to globally use nonnull as the default when
-		annotation-based null analysis is enabled. This implies that all types in method signatures without a null annotation are considered as specified non-null.</p>
-	</td>
-  </tr>
-  
-  <tr id="missing-non-null-by-default-annotation">
-    <td class="title">Detection of missing default nullness annotation</td>
-    <td class="content">
-    	In order to make non-null the default for un-annotated types in method signatures you may
-    	use the '@NonNullByDefault' annotation on all packages.
-        To ensure full coverage of all packages you can configure JDT to detect a missing default nullness annotation.
-        When <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings &gt; Null analysis &gt; Missing '@NonNullByDefault' annotation on package</b>
-        is enabled, JDT will issue an error/warning in the following cases:
-		<ul>
-		<li> When a package does not contain an '@NonNullByDefault' annotation in the package-info.java:
-		<p><img src="images/missing-nonnullbydefault-package.png" alt="Missing @NonNullByDefault annotation on package warning"/></p>
-		</li>
-		<li> When a type inside a default package does not contain a default nullness annotation.
-		<p><img src="images/missing-nonnullbydefault-type.png" alt="Missing @NonNullByDefault annotation on type warning"/></p>
-		</li>
-		</ul>
-	</td>
-  </tr>
-  
-    <tr id="Assert-like-java-assert-null-analysis">
-    <td class="title">Null analysis treats org.&#8203;eclipse.&#8203;core.&#8203;runtime.&#8203;Assert like Java assert</td>
-    <td class="content">
-        Since <b>org.eclipse.core.runtime.Assert</b> is often used just like the Java <b>assert</b> keyword, JDT's null analysis considers
-		the boolean expression passed into the former as always true after the Assert reference, since if the condition did turn out to be false,
-		the control flow will never go further than the org.eclipse.core.runtime.Assert reference.
-		<p><img src="images/assert-warnings.png" alt="Code snippet showing the boolean expression passed into org.eclipse.core.runtime.Assert.isLegal(..) is considered true after the call"/></p>
-	</td>
-  </tr>
-  
-  <tr id="pre-built-index-support">
-    <td class="title">Faster search with pre-built indexes</td>
-    <td class="content">
-        <i>Note: This feature is mainly intended for plug-ins that implement their own classpath container, not for the end user.</i>
-        <p>You can now tell JDT search to use pre-built indexes instead of having the compiler generate the indexes the first time a JAR is added to the classpath. 
-		This prevents indexing from occurring on the user's machine and lets the user obtain first search results faster.</p>
-		<p>You can specify the index file as a classpath attribute <code>IClasspathAttribute.INDEX_LOCATION_ATTRIBUTE_NAME</code> of the library.</p>
-		<p>See <b>Help &gt; JDT Plug-in Developer Guide &gt; Programmer's Guide &gt; JDT Core &gt; Indexes for the Java search</b> for more details.</p>
-	</td>
-  </tr>
-
-  <!-- ******************* Java Views and Dialogs ************************************* -->
-  <tr>
-    <td id="JavaViews" class="section" colspan="2">
-    <h2>Java Views and Dialogs</h2>
-    </td>
-  </tr>
-
-  <tr id="encoding-for-source-attachments">
-    <td class="title">Encoding for source attachments</td>
-    <td class="content">
-        You can now specify the encoding for source attachments for libraries e.g.
-		in <b>Build Path &gt; Libraries &gt;</b> expand the library <b>&gt; Source attachment &gt; Edit...</b>
-		<p><img src="images/source-attachment-encoding.png" alt="Dialog to specify encoding for source attachments."/></p>
-	</td>
-  </tr>
-  
-  <tr id="errors-warnings-highlight">
-    <td class="title">Highlighting on Errors/Warnings preference pages</td>
-    <td class="content">
-        On Errors/Warnings preference pages, it is sometimes hard to see which item is selected, especially
-        when you opened the dialog via the "Configure Problem Severity" button.
-        <p><img src="images/configure-problem-severity.png" alt="Configure Problem Severity button in Java Editor problem hover"/></p>
-        Now, an arrow highlights the selected item, and another arrow highlights the item under the mouse.
-        <p><img src="images/errors-warnings-highlight.png" alt="Highlighting in preference pages"/></p>
-        The highlighting also works on the PDE and API Tools preference pages.
-    </td>
-  </tr>
-
-  <!-- ******************* Properties File Editor ************************************* -->
-  <tr>
-    <td id="PropertiesEditor" class="section" colspan="2">
-    <h2>Properties File Editor </h2>
-    </td>
-  </tr>
-  
-  <tr id="JDT-property-key-quick-assists">
-    <td class="title">Quick assists to reorganize property keys</td>
-    <td class="content">
-      If you use Eclipse-style externalized strings, the following new quick assists make it easier to
-      reorganize keys inside the <b>Properties File Editor</b>:
-      <ul>
-          <li><b>Rename in workspace</b> - renames the key in the properties file and updates all references</li>
-          <li><b>Create field in '...'</b> - creates the corresponding field in the resource bundle accessor class</li>
-          <li><b>Remove property</b> - deletes the property from the properties file and the field from the resource bundle accessor class</li>
-          <li><b>Remove properties</b> - deletes the selected properties from the properties file and the fields from the resource bundle accessor class</li>
-      </ul>
-    </td>
-  </tr>
-
-  <!-- *********************** Debug ******************************** -->
-  <tr>
-    <td id="Debug" class="section" colspan="2">
-    <h2>Debug</h2>
-    </td>
-  </tr>
-
-  <tr id="export-detail-formatters">
-    <td class="title">Export detail formatters</td>
-    <td class="content">
-        Detail formatters (which are e.g. used to render objects in the Variables view) can now be exported as separate preferences. Previously, the only way to share detail formatters was to export
-        all of your workspace settings.    
-        <p><img src="images/detail-formatters.png" alt="Detail formatters in the export dialog"/></p>
-    </td>
-  </tr>
-
-  <tr id="show-monitors-default">
-    <td class="title">Show Monitors on by default</td>
-    <td class="content">
-      The default setting for displaying monitor information in the <b>Debug</b> view is now set to <em>on</em>.
-      This change only affects new workspaces and does not change existing settings.
-      <p>
-      Showing monitor information can be turned on or off using the <b>Java &gt; Show Monitors</b> view action
-      within the <b>Debug</b> view.
-      </p>
-    </td>
-  </tr>
-  <tr id="toggle-bp-mod-keys">
-    <td class="title">Toggle breakpoint modifier keys</td>
-    <td class="content">
-      There is now support for modifier keys while toggling breakpoints in the Java editor:
-      <ul>
-        <li><p>Holding the <b>Ctrl</b> key while double-clicking (toggling) a breakpoint will cause the <b>Properties 
-        dialog</b> for that breakpoint to be displayed (on the Mac, use <b>Command</b>)</p>
-        </li>
-        <li>Holding the <b>Alt</b> key while double-clicking (toggling) a breakpoint will <b>enable / disable</b> that breakpoint</li>
-      </ul>
-      If there is no existing breakpoint, a normal breakpoint toggle takes place even if a modifier key is held down.
-    </td>
-  </tr>
-
-  <!-- ******************* JUnit ************************************* -->
-  <tr>
-    <td id="JUnit" class="section" colspan="2">
-    <h2>JUnit</h2>
-    </td>
-  </tr>
-
-  <tr id="junit-4-10">
-    <td class="title">JUnit 4.10</td>
-    <td class="content">
-      The JUnit 4 version shipped with Eclipse has been updated to <a href="https://github.com/KentBeck/junit/blob/r4.10/doc/ReleaseNotes4.10.txt">4.10</a>.
-    </td>
-  </tr>
-
-    <!-- ****************** END OF N&N TABLE ****************** -->
-  </tbody>
-</table>
-
-<p align="center"><a href="eclipse-news-part1.html">Previous</a>&nbsp;&nbsp;&nbsp;&nbsp; <a href="eclipse-news-part3.html">Next</a></p>
-</body>
-
-</html>
diff --git a/platform/4.2/final/eclipse-news-part3.html b/platform/4.2/final/eclipse-news-part3.html
deleted file mode 100644
index f836871..0000000
--- a/platform/4.2/final/eclipse-news-part3.html
+++ /dev/null
@@ -1,571 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2012. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Juno - New and Noteworthy</title>
-</head>
-<body>
-
-<h2>Platform and Equinox API</h2>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table class="news" cellpadding="10" cellspacing="0">
-<tbody>
-  <!-- ******************** Platform ********************** -->
-  <tr>
-    <td id="Platform" class="section" colspan="2"><h2>Platform Changes</h2></td>
-  </tr>
-
-  <tr id="modeled-ui">
- <td class="title">Modeled user interface</td>
-    <td class="content">
-	 The Eclipse platform user interface is now
-	 represented internally as an EMF model. Applications can reconfigure or extend this 
-	 model to arrive at very different presentations of their application with no additional 
-	 coding required. Normalizing the workbench structure as a well defined model has 
-	 the added benefit of making the code for the workbench itself much simpler and less 
-	 error prone. Most importantly, this allows for very different workbench UI layouts, 
-	 such as parts living outside of perspectives, views and editors in dialogs, and other 
-	 designs not previously allowed by the older generation workbench with its rigid 
-	 hand-crafted model. Having a model also allows for more advanced tool support 
-	 for application designers, such as visual design tools. </td>
-	</tr>
-
-  <tr id="model-structure">
-    <td class="title">Clean model structure</td>
-    <td class="content">
-	The workbench model is separated into a number of different levels of building blocks. These are
-	sets of related model functionality that can be used to augment the basic capabilities of the RCP model
-	in order to enhance the UI. This allows RCP developers to choose the specific enhancements that they
-	really need rather than having to make an either/or choice between a model that is simplistic versus one
-	that can support the complete existing IDE UI. The categories are:
-	<ul>
-	<li>Menus and Toolbars: This is a fairly generic definition, suitable for directly implemented operations.</li>
-	<li>RCP: This is a Sash/Stack/Part containment model very much like the legacy one.</li>
-	<li>Commands: This is the e4 version of the Commands/Handlers/Bindings infrastructure. Use this model if you
-	need more sophisticated operations like key bindings, retargetable commands (Undo, copy...).</li>
-	<li>Trim: Using these elements allows clients to add trim containers on any side of their window and
-	populate them with ui elements.</li>
-	<li>Editing: This is a specific element used to gain access to the legacy editor behavior.</li>
-	<li>Shared Elements: These elements allow reuse of various model elements in different parts of the model.
-	It will be used in the compatibility layer for supporting the sharing of views and editor areas between
-	different perspectives.</li>
-	</ul>
-    </td>
-   </tr>
-
-	<tr id="presentation-engine">
-	 <td class="title">Pluggable presentation engine</td>
-    <td class="content">
-	 The workbench model is now translated into
-	 concrete widgets via a generic <i>presentation engine</i> API. The platform
-	 includes a default presentation engine that renders the model using traditional SWT
-	 widgets, but applications can employ alternate presentation engines to render their
-	 application model using a different widget toolkit.</td>
-	</tr>
-
-	<tr id="css-styling">
-	 <td class="title">Widget styling with CSS</td>
-    <td class="content">
-	 The workbench now defines a pluggable
-	 <i>styling engine</i> that allows the appearance of widgets to be customized
-	 declaratively using Cascading Style Sheets (CSS). Widget details such as fonts,
-	 colors, borders, and icons can now be customized via application-defined CSS files.
-	 This mechanism supports changing styles on the fly while the application is running.
-	 <p>
-	 The Eclipse SDK 4 includes styling data to implement the new IDE look and feel,
-	 but rich client applications can employ different CSS styling to achieve a significantly
-	 different widget appearance.
-	 </p>
-    <p><img src="images/cssexample.png" alt="Example of custom styling in contacts demo" /></p>
-	 </td>
-	</tr>
-	
-  <tr id="flexible-tab-rendering">
-    <td class="title">Flexible tab rendering</td>
-    <td class="content">
-    In the platform 3.6 release, SWT introduced API to allow a different renderer
-    for <tt>CTabFolder</tt> to be plugged in. The workbench now uses this pluggable
-    rendering to implement the new Eclipse 4 workbench look and feel.
-    <p><img src="images/ctabrender.png" alt="Highlight of custom tab rendering" /></p></td>
-  </tr>
-
-	<tr id="contexts"> 
-    <td class="title">Hierarchical contexts</td>
-    <td class="content">
-    The bundle <tt>org.eclipse.e4.core.contexts</tt>
-    introduces the notion of hierarchical contexts via the <tt>IEclipseContext</tt> API.
-    Contexts provide a mechanism for isolating application code from the framework,
-    providing an abstraction through which application code can obtain objects and
-    services from the framework. Contexts also provide a way for application code 
-    to make data and services available to other application code in a loosely coupled manner.
-    Contexts currently support:
-    <ul>
-    <li>Context hierarchies. Contexts can be nested within a parent context to override
-    services provided by their parent. This enables application code written in one context
-    to be easily transferred to work in different contexts.</li>
-    <li>OSGi service lookup. Contexts can be used to obtain references to OSGi services.
-    The context takes care of tracking dynamic service changes and cleaning up unused
-    services when contexts are discarded.</li>
-    <li>Dependency injection. Values from a context can be injected into an application object. This
-    results in injectable fields and methods in the application object being provided with
-    values defined in the context. Injection completely removes direct dependency from
-    application code onto the framework.</li>
-    <li>Storage of functions. Contexts can store functions that are evaluated lazily
-    to obtain context values. A client retrieving values from a context may be obtaining
-    raw values stored in the context, or the result of some function that was evaluated
-    at the time of the context lookup.</li>
-    <li>Traditional change notification, and registration of data-binding style update code with a context.
-    Each time the registered update code is run, the context tracks which context values
-    were referenced. Subsequent changes to any of those values will result in the update
-    code re-running. Updates and events are batched and queued to avoid superfluous
-    notifications.</li>
-    </ul></td>
-	</tr>
-
-	<tr id="part-services-using-contexts"> 
-     <td class="title">UI service lookup via contexts</td>
-    <td class="content">
-     The workbench provides a hierarchy of service
-     contexts that reflects the widget hierarchy of the workbench itself. Thus when a 
-     part obtains a service or data value from its context, it will correctly reflect the
-     widget containment structure of that part. This allows parts to be reused in
-     novel new widget layouts without requiring changes in the part's code.</td>
-	</tr>
-
-  <tr id="jsr-330-injection"> 
-    <td class="title">javax.inject annotation support</td>
-    <td class="content">
-    Context injection supports
-    the annotations defined in the upcoming <code>javax.inject</code> package.
-	Annotations such as <code>@Inject</code> and <code>@Named</code> can be used
-	to describe context elements to inject. The internal 
-	injection processing has been updated to make use of these annotations, and
-	passes the open source annotation-based injection test suite found at 
-	<a href="http://code.google.com/p/atinject/">http://code.google.com/p/atinject/</a>.
-	<p>
-	As a result of this work the dependency injection implementation is available
-	as an independent service. While the exact APIs are still under construction and will change, 
-	we expect to make the <code>javax.inject</code>-based dependency injection available as one of 
-	the core Eclipse 4 application platform services.  
-    </p>
-    </td>
-  </tr>
-
-  <tr id="event-bus">
-    <td class="title">Common event bus</td>
-    <td class="content">
-	The Eclipse workbench now has an event bus style architecture based on the 
-	publish/subscribe pattern. This means a 'one stop shopping' approach for
-	workbench clients; <i>any</i> user interface event we expect a client to be interested in 
-	(UI model changes, part life-cycle events, etc) will be available through a
-	common mechanism simply by registering an event handler against the
-	appropriate topic.
-	<p><img src="images/event-bus.png" alt="Event bus"/></p>
-    </td>
-  </tr>
-
-  <tr id="git-migration">
-    <td class="title">Git migration</td>
-    <td class="content">
-    During this release cycle, the Eclipse and Equinox projects migrated their source control systems to <a href="http://git-scm.com/">Git</a>.
-    The new Git repositories are now available for developers to clone or fork:
-    <ul>
-    <li><a href="http://git.eclipse.org/c/platform">Platform</a></li>
-    <li><a href="http://git.eclipse.org/c/jdt">Java development tools</a></li>
-    <li><a href="http://git.eclipse.org/c/pde">Plugin Development Environment</a></li>
-    <li><a href="http://git.eclipse.org/c/equinox">Equinox</a></li>
-    </ul>
-    </td>
-  </tr>
-
-  <tr id="flexible-viewer-refactor">
-    <td class="title">Flexible viewer refactored</td>
-    <td class="content">
-      The code driving the debug views (Debug, Variables and Breakpoints) has been substantially refactored to improve its overall quality, stability and
-      performance. 
-      <br/><br/>
-      Some of the more notable changes include:
-      <ul>
-        <li>There is a 30% improvement in the overall performance of the views</li>
-        <li>Two new interfaces have been added to the provisional API: <code>IModelProxyFactory2</code> and <code>ITreeModelViewer</code></li>
-        <li>The <b>Copy</b> and <b>Find</b> actions have been re-written to work better with the virtual views</li>
-        <li>A new viewer filter extension has been added to <code>TreeModelViewerFilter</code>, mitigating scrollbar presentation issues</li>
-      </ul> 
-      The complete list of changes can be found <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=161435#c47">here</a>.
-    </td>
-  </tr>
-
-  <tr id="workbench-events-refactoring">
-    <td class="title">Refactored Eclipse 4 Event API</td>
-    <td class="content">
-      Workbench UI events have been refactored to make them easier to understand and use.  
-      For a detailed write up on the Eclipse 4 event model and the changes in this release 
-      please take a look at <a href="http://wiki.eclipse.org/Eclipse4/RCP/Event_Model">http://wiki.eclipse.org/Eclipse4/RCP/Event_Model</a> and 
-      <a href="http://wiki.eclipse.org/Eclipse4/UI/Event/Migration">http://wiki.eclipse.org/Eclipse4/UI/Event/Migration</a>.
-    </td>
-  </tr>
-
-  <tr id="trim-styling">
-    <td class="title">Trim styling</td>
-    <td class="content">
-      In the new window trim implementation, the drag handle and the frame surrounding the trim are 
-      defined through CSS. Here's an example of what this looks like:
-<pre>
-.MToolControl.TrimStack {
-	frame-image:  url(./winXPTSFrame.PNG);
-	handle-image:  url(./winXPHandle.PNG);
-	frame-cuts: 5px 1px 5px 16px;
-}
-</pre>
-	  <p><tt>frame-image</tt> and <tt>handle-image</tt> define the images to be used to draw the frame. 
-	  The <tt>frame-cuts</tt> attribute is a set of 4 integer values that are used to divide the <tt>frame-image</tt>
-	  into specific areas by defining two widths and two heights (the third is just the image size minus the 
-	  sum of the other two. This allows us to determine what part of the image to use for the top/right corner.</p>
-	  <p>Here is a more interesting example that illustrates the power this gives to applications to customize their appearance:</p>
-      <p><img src="images/trim-styling.png" alt="Trim styling"/></p> 
-    </td>
-  </tr>
-
-  <tr id="css-theme-event">
-    <td class="title">CSS-based Theme changed event</td>
-    <td class="content">
-      An OSGi EventAdmin-based event is now raised on theme change.
-      Subscribe to the <tt>IThemeEngine.Events.THEME_CHANGED</tt> topic to be notified when the workbench theme is changed.
-    </td>
-  </tr>
-
-  <tr id="css-extension-points">
-    <td class="title">Changes to CSS extension points</td>
-    <td class="content">
-      For those providing extensions for the new CSS support,
-      the extension points for providing property handlers and
-      element providers have been renamed to
-      <tt>org.eclipse.e4.ui.css.core.propertyHandler</tt> and
-      <tt>org.eclipse.e4.ui.css.core.elementProvider</tt>
-      (respectively).
-    </td>
-  </tr>
-
-  <tr id="relaunchlast-api">
-    <td class="title">RelaunchLastAction has been made API</td>
-    <td class="content">
-      The internal class <code>RelaunchLastAction</code> has been promoted to API and can be found in the 
-      <code>org.eclipse.debug.ui.actions</code> package.
-    </td>
-  </tr>
-
-  <tr id="expression-view-constant-api">
-    <td class="title">Add new expression image constant has been made API</td>
-    <td class="content">
-      The constant <code>IDebugUIConstants.IMG_OBJ_ADD_NEW_EXPRESSION</code> has been added to API to allow consumers who 
-      extend or use the <b>Expressions</b> view look-and-feel to use the <b>Add New Expression</b> icon 
-      (<img src="images/monitorexpression_tsk.gif" alt="The add new expression icon"/>).
-    </td>
-  </tr>
-
-  <tr id="toggle-bp-target-mgr-api">
-    <td class="title">Toggle breakpoints target manager has been made API</td>
-    <td class="content">
-      The interface <code>org.eclipse.debug.ui.actions.IToggleBreakpointsTargetManager</code> has been made API to allow clients
-      access to known <code>IToggleBreakpointTarget</code>s. The new API can be accessed via 
-      <code>org.eclipse.debug.ui.DebugUITools#getToggleBreakpointsTargetManager()</code>
-    </td>
-  </tr>
-  
-  <tr id="bp-types-contribution-api">
-    <td class="title">BreakpointTypesContribution has been made API</td>
-    <td class="content">
-    The class <code>org.eclipse.debug.ui.actions.BreakpointTypesContribution</code> has been added to API. This class 
-    can be reused by clients to add a breakpoint type action in the editor gutter context menu to match the action(s) that appear in the 
-    <b>Run &gt; Breakpoint Types</b> menu. 
-    </td>
-  </tr>
-
-  <tr id="var-view-find-override">
-    <td class="title">Find action can be customised in Variables View specialisations</td>
-    <td class="content">
-    Consumer now have the ability to completely override the behaviour of the <b>Find...</b> action in the <b>Variables View</b> and any of
-    its sub-classes, e.g. <b>Expressions View</b>, <b>Modules View</b>, etc.
-    <p>
-    To replace the default <b>Find...</b> actions clients must provide an adapter for the 
-    interface <code>org.eclipse.debug.internal.ui.viewers.model.provisional.IViewActionProvider</code>.
-    </p>
-    <p>
-    For more information see the Javadoc for <code>org.eclipse.debug.internal.ui.viewers.model.provisional.IViewActionProvider</code>
-    with an example available in the <code>org.eclipse.debug.examples.ui</code> bundle found in the Platform Debug Git repo.
-    </p>
-    </td>
-  </tr>
-
-  <!-- ******************** Equinox ********************** -->
-  <tr>
-    <td id="Equinox" class="section" colspan="2"><h2>Equinox Changes</h2></td>
-  </tr>
-
-  <tr id="Equinox-console">
-    <td class="title">New OSGi console</td>
-    <td class="content">
-      This release includes a brand new OSGi console based on the Apache Felix Gogo project.
-	  In previous releases the Equinox framework contained a built-in OSGi console. 
-	  This console allows you to interact with the OSGi framework and execute commands 
-	  on the running instance of the framework. For example, it can be used to install bundles 
-	  or to get a list of currently installed bundles. The built-in console is convenient because 
-	  it is always available without needing to install extra bundles, but it is also limited
-	  because the framework itself must contain all the functionality of the built-in console. 
-	  <p>
-      The Apache Felix Gogo project has developed an advanced shell for interacting with OSGi frameworks. 
-      Instead of continually enhancing the built-in Equinox Framework console, a new external Equinox 
-      Console bundle has been created that uses the Apache Felix Gogo bundles. The new Equinox Console 
-      bundle continues to provide support for the Equinox Console APIs (package 
-      <tt>org.eclipse.osgi.framework.console</tt>). It also adds many new enhancements which are 
-      possible through the use of the Gogo shell. This includes features such as tab completion, 
-      command history, piping, grep, telnet and ssh connections, and more. Type <i>help</i> on the console 
-      to see a list of available commands, or <i>help &lt;command-name&gt;</i> for information on 
-      how to use each command.
-      </p>
-    </td>
-  </tr>
-
-  <tr id="jetty">
-    <td class="title">Update to Jetty 8 and Servlet 3.0</td>
-
-    <td class="content">
-      The Equinox HTTP service implementation is now using Jetty 8 as the
-      web container to support Servlet 3.0 and JSP 2.2.  The Equinox HTTP
-      service is required to host the Eclipse user assistence web context
-      for serving up help content.
-      <p>
-      For the Juno release, Equinox will no longer support the use of older
-      Jetty implementations and we are no longer shipping Jetty 6.  The
-      Equinox HTTP service implementation will no longer work with the
-      Servlet 2.5 and JSP 2.1 APIs.  Also note that the 
-      Jasper and expresson language implementation bundles
-      have changed in order to support the Servlet 3.0 and JSP 2.2 
-      specifications.  The following bundles have been removed:
-      <ul>
-        <li>org.apache.jasper</li>
-        <li>org.apache.commons.el</li>
-        <li>org.mortbay.jetty.server</li>
-        <li>org.mortbay.jetty.util</li>
-      </ul>
-      These have been replaced with the following to support Servlet 3.0
-      and JSP 2.2:
-      <ul>
-        <li>org.eclipse.jetty.continuation</li>
-        <li>org.eclipse.jetty.http</li>
-        <li>org.eclipse.jetty.io</li>
-        <li>org.eclipse.jetty.security</li>
-        <li>org.eclipse.jetty.server</li>
-        <li>org.eclipse.jetty.servlet</li>
-        <li>org.eclipse.jetty.util</li>
-        <li>javax.el</li>
-        <li>org.apache.jasper.glassfish</li>
-        <li>com.sun.el</li>
-      </ul>
-      </p>
-    </td>
-  </tr>
-
-  <tr id="pref-storage">
-    <td class="title">Customize storage for preference scopes</td>
-    <td class="content">
-      When defining your own preference scope, you can now extend a simple storage
-      customization class rather than implementing all the preference logic yourself. In this class you
-      simply define the code to read and write a preference node to whatever backing store you want to use.
-      This makes it very easy to define a custom preference scope with alternate storage
-      requirements. For more details see the documentation for the <tt>org.eclipse.equinox.preferences.preferences</tt>
-      extension point, or the new API class <tt>org.eclipse.core.runtime.preferences.AbstractPreferenceStorage</tt>.
-    </td>
-  </tr>
-
-  <tr id="osgi-core-5">
-    <td class="title">OSGi Core Release 5</td>
-    <td class="content">
-      With this release the Equinox OSGi Framework implements the 
-      draft OSGi Core Release 5 (R5) specification.  The OSGi Core 
-      R5 specification is an incremental change from the R4.3 
-      specification.  A majority of the changes included in
-      the Core R5 specification are in support of the upcoming
-      OSGi Enterprise Release 5 specification.  A public draft of
-      the specification will be available 
-      <a href="http://www.osgi.org/Specifications/Drafts">here</a>
-      by March 26, 2012.  The final version will be available 
-      <a href="http://www.osgi.org/Download/File?url=/download/osgi.core-5.0.0-pfd.pdf">here</a>
-      shortly after that.
-    </td>
-  </tr>
-  <tr id="publisher-negation-requirements">
-    <td class="title">Publisher Support for Negation Requirements</td>
-    <td class="content">
-      The p2 publisher can now publish <b>negation</b> requirements.
-      A negation requirement is a requirement that <b>must not</b>
-      be present.  For example, the Rich Ajax Platform (RAP) can 
-      declare a negation requirement on the Eclipse Platform, meaning
-      that RAP won't be installable into your IDE.<br/>
-      Negation requirements are specified using the p2.inf file.  
-      Details are available on the <a href="http://wiki.eclipse.org/Equinox/p2/Customizing_Metadata#Capability_Advice:">Wiki</a>
-    </td>
-  </tr>
-
-  <!-- *********************** SWT *********************** -->
-  <tr>
-    <td id="SWT" class="section" colspan="2"><h2>SWT Changes</h2></td>
-  </tr>
-
-  <tr id="SWT-cocoa-highlight">
-    <td class="title">Highlight TrayItem Image</td>
-    <td class="content">You can now provide a custom image for use as the hightlight image for 
-    a tray item on Cocoa. The highlight image is shown when the tray item is activated. 
-    The default tray item image will be restored when the tray item is deactivated.
-    <p><i>Default Tray Item</i><br/><img src="images/nohighlight.png" alt="Default Tray Item"/></p>
-    <p><i>Highlighted Tray Item</i><br/><img src="images/highlight.png" alt="Highlighted Tray Item"/></p>
-    </td>
-  </tr>
-  <tr id="SWT-styledtext-scrollbars">
-    <td class="title">Added support in StyledText to show the scrollbars only when needed</td>
-    <td class="content">In the past, when a StyledText was created with scrollbars it would show 
-    them all the time, even when the client area was big enough to show the entire content.
-    By using <code>setAlwaysShowScrollBars()</code> this behaviour can now be configured so that 
-    instead of showing a disabled scrollbar, the StyledText will only display the scrollbar when needed.
-    </td>
-  </tr>
-  <tr id="SWT-styledtext-events">
-    <td class="title">Event type constants in StyledText are now public</td>
-    <td class="content">
-    The following event type constants in <tt>StyledText</tt> have been made public:
-    <ul>
-    <li>ExtendedModify</li>
-    <li>LineGetBackground</li>
-    <li>LineGetStyle</li>
-    <li>TextChanging</li> 
-    <li>TextSet</li>
-    <li>VerifyKey</li>
-    <li>TextChanged</li>
-    <li>LineGetSegments</li>
-    <li>PaintObject</li>
-    <li>WordNext</li>
-    <li>WordPrevious</li>
-    <li>CaretMoved </li>
-    </ul>
-    This allows these constants to be used with <tt>Widget#isListening()</tt> to verify if a 
-    listener handler was added for any event type in <tt>StyledText</tt>.
-    </td>
-  </tr>
-  <tr id="SWT-default-browser">
-      <td class="title">Default Browser renderer is now configurable</td>
-    <td class="content">
-    The native renderer that is used for <code>SWT.NONE</code>-style browsers can now be 
-    configured by setting a Java property. This is particularly important for applications 
-    that create browsers with a specific native renderer style (eg.- <code>SWT.MOZILLA</code>), 
-    in order to avoid conflicts that can occur when multiple native renderers are loaded in 
-    the same process.
-    <p>For more information on using this new property see 
-    <a href="http://www.eclipse.org/swt/faq.php#browserspecifydefault">How do I specify the 
-    default type of native renderer that is used by the Browser?</a> .</p>
-   </td>
-  </tr>
-  <tr id="SWT-fontdialog">
-    <td class="title">FontDialog Effects</td>
-    <td class="content">
-    New API has been added to <tt>FontDialog</tt> to prevent the user from selecting font effects,
-    such as color, underline, strikethrough and shadow.
-    <p><img src="images/font-dialog-effects.png" alt="FontDialog on Windows without the Effects grouping"/></p>
-    </td>
-  </tr>
-  <tr id="SWT-combo-api">
-    <td class="title">New Combo API</td>
-    <td class="content">
-    Two new APIs have been added to <tt>Combo</tt> that allow users to get the caret information 
-    in a combo box. <code>Combo.getCaretLocation</code> returns the pixel coordinates of the 
-    caret. <code>Combo.getCaretPosition</code> returns the character position of the caret.
-    <p>
-    For an example of how to use this API see 
-    <a href="http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/examples/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet359.java">Snippet 359</a>.
-    </p>
-    </td>
-  </tr>
-
-	<tr id="swt-tree-cursor">
-      <td class="title">Tree Cursor</td>
-      <td class="content">
-      The new <tt>TreeCursor</tt> class can be used to enable users to navigate a <tt>Tree</tt> control's individual 
-      cells, similar to what <tt>TableCursor</tt> makes possible for <tt>Table</tt> controls.  For an example of 
-      using <tt>TreeCursor</tt> see <a href="http://git.eclipse.org/c/platform/eclipse.platform.swt.git/plain/examples/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet360.java">Snippet360</a>.
-      <p><img src="images/treecursor.png" alt="Tree Cursor"/></p>
-      </td>
-  </tr>
-
-  <tr id="XULRunner">
-    <td class="title"> XULRunner 10</td>
-    <td class="content">
-      The SWT browser now supports embedding XULRunner 10.0.x (note that XULRunner versions 4.x - 9.x are not supported).  
-      Apps wishing to use this must ship a XULRunner 10 runtime and explicitly point at it as described in 
-      <a href="http://www.eclipse.org/swt/faq.php#specifyxulrunner">the FAQ</a> .
-    </td>
-  </tr>
- 
-  <tr id="ContextMenuTrigger">
-    <td class="title">Provide context menu trigger</td>
-    <td class="content">
-      <tt>MenuDetectEvent</tt> now fills in the event <tt>detail</tt> field to indicate
-      whether the context menu is being triggered by the <tt>SWT.MENU_MOUSE</tt> or <tt>SWT.MENU_KEYBOARD</tt>.
-      If the <tt>event.detail</tt> is <tt>SWT.MENU_KEYBOARD</tt>, custom controls can appropriately position
-      the context menu based on current focus or selection.
-    </td>
-  </tr>
-  <tr id="CustomColors">
-    <td class="title">Set/get custom colors in ColorDialog</td>
-    <td class="content">
-      <tt>ColorDialog</tt> now supports <tt>getRGBs()</tt> and <tt>setRGBs(RGB [])</tt> to allow applications
-      to retrieve, save, and restore any custom colors that the user selected in the dialog.
-      <p><img src="images/custom-colors.png" alt="Custom Colors section of a win32 ColorDialog"/></p>
-    </td>
-  </tr>
-
-  <tr id="BIDI">
-    <td class="title">BIDI segments on text widget</td>
-    <td class="content">
-      The <tt>Text</tt> widget now supports adding <tt>SegmentListener</tt> for BIDI support. This allows BIDI ordering to be applied to segments of the text instead of the entire text.
-    </td>
-  </tr>
-  
-  <tr id="Browser">
-    <td class="title">Browser Function Access</td>
-    <td class="content">
-      <tt>BrowserFunction</tt> can now be installed into specific frames.
-    </td>
-  </tr>
-  
-  <tr id="JarLoading">
-    <td class="title">SWT Runtime introspection</td>
-    <td class="content">
-      <tt>SWT.isLoadable()</tt> can be used to determine whether the SWT implementation can be loaded in the current running environment.
-    </td>
-  </tr>
-
-  <tr id="Overlay">
-    <td class="title">Overlay scrollbars</td>
-    <td class="content">
-      <tt>Scrollable.getScrollbarsMode()</tt> can be used to determine whether the platform shows overlay scrollbars.
-    </td>
-  </tr>
-
-  </tbody>
-<!-- ****************** END OF N&N TABLE ****************** -->
-</table>
-
-<p align="center"><a href="eclipse-news-part2.html">Previous</a>&nbsp;&nbsp;&nbsp;&nbsp; <a href="eclipse-news-part4.html">Next</a></p>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/platform/4.2/final/eclipse-news-part4.html b/platform/4.2/final/eclipse-news-part4.html
deleted file mode 100644
index 94639a2..0000000
--- a/platform/4.2/final/eclipse-news-part4.html
+++ /dev/null
@@ -1,188 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2012. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Juno - New and Noteworthy</title>
-</head>
-<body>
-<div style="font-size: 20px; font-weight: bold;">Plug-in Development Environment</div>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table class="news" cellpadding="10" cellspacing="0">
-      <!-- ******************* Views/Editors ******************** -->
-  <tr>
-    <td id="ViewsAndEditors" class="section" colspan="2">
-      <h2>
-        Views and editors
-      </h2>
-    </td>
-  </tr>
-
-  <tr id="vendor-history">
-    <td class="title">Plug-in vendor history</td>
-    <td class="content">
-      When creating a new plug-in, fragment or feature the Vendor information used in the creation wizard is retained and can be reused
-      by selecting the drop-down in subsequent uses of the wizard.
-      <p>
-        <img src="images/pde-wizard.png" alt="The Vendor history drop-down"/>
-      </p>
-    </td>
-  </tr>
-
-  <tr id="pde-import-package-explorer">
-    <td class="title">Import from repository in the Package Explorer view</td>
-    <td class="content">
-		 By using <b>File &gt; Import... &gt; Import Plug-ins and Fragments</b> you can import the source
-		 code for a plug-in from your installation if the plug-in has the necessary manifest header.
-		 Now you can access this functionality directly from the Package Explorer and Project Explorer
-		 views.  Right click on a plug-in in your project's <b>Plug-in Dependencies</b> classpath container
-		 and select <b>Import from Repository...</b>.
-
-		 <p><img src="images/import-repo-pkg.png" alt="Import from repository in package explorer view"/></p>
-
-		 <p>Importing from a repository is also available in the Target Platform State, Plug-in Dependencies and Plug-ins 
-		 views.  If the selected item can be imported, there will be an <b>Import As</b> menu visible when right clicking in
-		 the view.</p>
-
-		 <p><img src="images/import-repo-tps.png" alt="Import from repository in target platform state view"/></p>
-	</td>
-  </tr>
-  
-  <tr id="TracingPage">
-      <td class="title">Tracing preference page</td>
-      <td class="content">
-        A new preference page is available to dynamically set the debug tracing options for Eclipse.  You can turn on individual tracing options and the changes will take effect immediately.  There is no need to restart Eclipse.
-
-	<p><img src="images/tracing_page.png" alt="Tracing preference page"/></p>
-	<p>To add a plug-in's tracing options to the page, you must provide an <code>org.eclipse.ui.trace.traceComponents</code> extension. Your bundle must also register an <code>org.eclipse.osgi.service.debug.DebugOptionsListener</code> to be notified when tracing options are changed.</p>
-	<p>The preference page can be included in other products.  It is contained in the <code>org.eclipse.ui.trace</code> plug-in and has no dependencies on PDE.</p>
-      </td>
-  </tr>
-
-  <tr id="product-add-required">
-    <td class="title">Add required in feature based product</td>
-    <td class="content">
-     The product editor now has an <b>Add Required</b> button when editing a feature based product.  Pressing the button will add all the features that are required by the features already in the product configuration.
-     <p><img src="images/addrequired.png" alt="Add required button"/></p>
-    </td>
-  </tr>
-
-  <tr id="extensions-editor-enhancements">
-    <td class="title">Extension editor enhancements</td>
-    <td class="content">
-     Several improvements have been made to the extensions tab of the <b>Plug-in Editor</b>.
-     <p><img src="images/extensions_page.png" alt="Extensions editor enhancements"/></p>  
-    <ul>
-      <li><b>Filter related:</b> Available by right clicking and pressing <b>Filter Related</b>, only extensions that are related (same id, label, class, etc) will be displayed in the tree</li>
-      <li><b>Filter enhancements:</b> The standard filter textbox now supports multiple filters separated by "/", matches are bolded, and the filter applies to extension attributes</li>
-      <li><b>Label improvements:</b> More items will display icons and labels, class names are displayed without package name</li>
-      <li><b>Accelerated scrolling:</b> Pressing <b>Ctrl</b> while scrolling does fast scrolling</li>
-      <li><b>Better expansion:</b> The expand state of selected items can be toggled with a new action</li>
-    </ul>
-    </td>
-  </tr>
-
-  <tr id="workspace-deletion-cancel">
-    <td class="title">Workspace deletion is cancelable</td>
-    <td class="content">
-     Eclipse and OSGi launch configurations have the option to delete the workspace and configuration folders before launching.  This can be a long running operation with large workspaces.  The operation is now cancelable which will stop the launch.
-    </td>
-  </tr>
-
-      <!-- ***************** Target Platform ******************* -->
-      <tr>
-        <td id="TargetPlatform" class="section" colspan="2">
-          <h2>
-            Target Platform
-          </h2>
-        </td>
-      </tr>
-
-  <tr id="custom-target-locations">
-    <td class="title">Custom target locations</td>
-    <td class="content">
-	You can now provide custom locations for target definitions.  They appear in both the target 
-	definition editor and wizard along with the platform provided target locations: directory, installation, 
-	feature and software site.
-	<p>To provide a custom location, you must implement <tt>ITargetLocation</tt> and extend the extension point 
-	<tt>org.eclipse.pde.core.targetLocations</tt>.  To provide labels, wizards and other user interface elements, 
-	you must extend an additional extension point <tt>org.eclipse.pde.ui.targetLocationProvisioners</tt> and have 
-	your <tt>ITargetLocation</tt> implementation adapt to several types.  For additional details, view the Javadoc on 
-	<tt>ITargetLocation</tt>.</p>
-	</td>
-  </tr>
-
-  <tr id="pde-classpath-api">
-    <td class="title">Bundle classpath resolution API</td>
-    <td class="content">
-	The <b>org.eclipse.pde.core.bundleClasspathResolvers</b> extension point allows 
-	you to dynamically add additional content to the runtime classpath and source 
-	lookup path of workspace plug-ins at launch time.
-	</td>
-  </tr>
-
-  <tr id="NonJarTargetPlugins">
-      <td class="title">Non *.jar plug-ins in target platform</td>
-      <td class="content">
-	The target platform will now recognize archive files with any file extension as long as they contain a manifest with the necessary OSGi headers. Previously, PDE only supported directory plug-ins and jarred (*.jar) plug-ins.
-      </td>
-  </tr>
-
-  <tr id="target-configure-phase">
-    <td class="title">Target definition configure phase</td>
-    <td class="content">
-     When working with a target definition containing a software site location (such as a p2 repository) it is now possible to change whether the p2 configuration phase should be run when resolving the target.  By default the configuration phase is not included.  Changing the setting will change all locations in the target definition.
-     <p><img src="images/configurephase.png" alt="Configure phase option"/></p>
-    </td>
-  </tr>
-      
-      <!-- ******************** API Tools ********************** -->
-
-      <tr>
-        <td id="APITools" class="section" colspan="2">
-
-          <h2>
-            API Tools
-          </h2>
-        </td>
-      </tr>
-
-  <tr id="api-tracing">
-    <td class="title">API Tools tracing</td>
-    <td class="content">
-     API Tools has added all debug tracing settings to the <b>Tracing</b> preference page where they can be enabled and disabled as needed without restarting.
-     <p><img src="images/api_tracing.png" alt="API Tools tracing"/></p>
-    </td>
-  </tr>
-
-  <tr id="ee-cleanup">
-    <td class="title">EE descriptions updated</td>
-    <td class="content">
-     The API Tools execution environment descriptions have been
-     updated with more accurate package information and have been renamed for easier installation.
-     To turn on warnings for invalid references to classes or methods that are not available in the configured execution environment, use the
-     <b>Plug-in Development &gt; API Errors/Warnings</b> preference page.
-     <p>The execution environment descriptions can be installed from the Eclipse update site
-     (<a href="http://download.eclipse.org/eclipse/updates/4.2">http://download.eclipse.org/eclipse/updates/4.2</a>)
-     under the <b>API Tools Execution Environment Descriptions</b> category.</p>
-     <p><img src="images/eedesc.png" alt="Updated EE descriptions"/></p>
-    </td>
-  </tr>
-
-    <!-- ****************** END OF N&N TABLE ****************** -->
-</table>
-
-<p align="center"><a href="eclipse-news-part3.html">Previous</a>&nbsp;&nbsp;&nbsp;&nbsp; <font color="#808080">Next</font></p>
-
-</body>
-</html>
diff --git a/platform/4.2/final/eclipse-news.html b/platform/4.2/final/eclipse-news.html
deleted file mode 100644
index 0e7d921..0000000
--- a/platform/4.2/final/eclipse-news.html
+++ /dev/null
@@ -1,38 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2012. This page is made available under license. For full details see: http://www.eclipse.org/legal/notice.html" >
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse Juno - New and Noteworthy</title>
-</head>
-<body>
-
-<h1>Eclipse Juno - New and Noteworthy</h1>
-
-<div align="right"><i>
-Here Sidonian Dido was establishing a great temple<br>
-to Juno, rich with gifts and divine presence,<br>
-with bronze entrances rising from stairways, and beams<br>
-jointed with bronze, and hinges creaking on bronze doors.<br>
-</i>- <strong>Virgil</strong>, Aeneid, Book 1 lines 446-449<br><br></div>
-
-<p>Welcome to Juno, the simultaneous Eclipse release for 2012, including
-content from seventy two Eclipse projects. Two
-versions of the Eclipse platform have been included in this release: the primary 4.2 version, available
-from the <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">Eclipse Project downloads page</a>,
-and the legacy 3.8 version, available from the <a href="http://download.eclipse.org/eclipse/downloads/eclipse3x.php">3.x stream download page</a>.
-Here are some of the more noteworthy things available in the twelvth annual release of the Eclipse project SDK.</p>
-
-<blockquote>
-  <ul>
-    <li><a href="eclipse-news-part1.html">New features in the Platform and Equinox</a></li>
-    <li><a href="eclipse-news-part2.html">New features for Java developers</a></li>
-    <li><a href="eclipse-news-part3.html">New APIs in the Platform and Equinox</a></li>
-    <li><a href="eclipse-news-part4.html">New features for plug-in developers</a></li>
-  </ul>
-</blockquote>
-
-</body>
-</html>
diff --git a/platform/4.2/final/images/add-buildfiles.png b/platform/4.2/final/images/add-buildfiles.png
deleted file mode 100644
index 8cefebd..0000000
--- a/platform/4.2/final/images/add-buildfiles.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/addrequired.png b/platform/4.2/final/images/addrequired.png
deleted file mode 100644
index e6d04a8..0000000
--- a/platform/4.2/final/images/addrequired.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/ant-extension-assist.png b/platform/4.2/final/images/ant-extension-assist.png
deleted file mode 100644
index 1246bf0..0000000
--- a/platform/4.2/final/images/ant-extension-assist.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/api_tracing.png b/platform/4.2/final/images/api_tracing.png
deleted file mode 100644
index 2517db4..0000000
--- a/platform/4.2/final/images/api_tracing.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/area.png b/platform/4.2/final/images/area.png
deleted file mode 100644
index 0479355..0000000
--- a/platform/4.2/final/images/area.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/assert-warnings.png b/platform/4.2/final/images/assert-warnings.png
deleted file mode 100644
index edc9a1e..0000000
--- a/platform/4.2/final/images/assert-warnings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/bp-sorting.png b/platform/4.2/final/images/bp-sorting.png
deleted file mode 100644
index c5502f2..0000000
--- a/platform/4.2/final/images/bp-sorting.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/bracket-highlighting-preferences.png b/platform/4.2/final/images/bracket-highlighting-preferences.png
deleted file mode 100644
index 785f838..0000000
--- a/platform/4.2/final/images/bracket-highlighting-preferences.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/bracket-hover-1.png b/platform/4.2/final/images/bracket-hover-1.png
deleted file mode 100644
index 19d1d45..0000000
--- a/platform/4.2/final/images/bracket-hover-1.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/bracket-hover-2.png b/platform/4.2/final/images/bracket-hover-2.png
deleted file mode 100644
index 3b5668b..0000000
--- a/platform/4.2/final/images/bracket-hover-2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/buildpath-error.png b/platform/4.2/final/images/buildpath-error.png
deleted file mode 100644
index f7e4be8..0000000
--- a/platform/4.2/final/images/buildpath-error.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/configure-problem-severity.png b/platform/4.2/final/images/configure-problem-severity.png
deleted file mode 100644
index 4084cb2..0000000
--- a/platform/4.2/final/images/configure-problem-severity.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/configurephase.png b/platform/4.2/final/images/configurephase.png
deleted file mode 100644
index 577145d..0000000
--- a/platform/4.2/final/images/configurephase.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/content-assist-pkg-info.png b/platform/4.2/final/images/content-assist-pkg-info.png
deleted file mode 100644
index e72b537..0000000
--- a/platform/4.2/final/images/content-assist-pkg-info.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/context-menu.png b/platform/4.2/final/images/context-menu.png
deleted file mode 100644
index 864d9cc..0000000
--- a/platform/4.2/final/images/context-menu.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/convert-to-for-loop.png b/platform/4.2/final/images/convert-to-for-loop.png
deleted file mode 100644
index ef74a8e..0000000
--- a/platform/4.2/final/images/convert-to-for-loop.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/cssexample.png b/platform/4.2/final/images/cssexample.png
deleted file mode 100644
index cd64a45..0000000
--- a/platform/4.2/final/images/cssexample.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/ctabrender.png b/platform/4.2/final/images/ctabrender.png
deleted file mode 100644
index c8f5cd6..0000000
--- a/platform/4.2/final/images/ctabrender.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/custom-colors.png b/platform/4.2/final/images/custom-colors.png
deleted file mode 100644
index 9869c03..0000000
--- a/platform/4.2/final/images/custom-colors.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/debug-trace.png b/platform/4.2/final/images/debug-trace.png
deleted file mode 100644
index a01d0c3..0000000
--- a/platform/4.2/final/images/debug-trace.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/debug_toolbar-1.png b/platform/4.2/final/images/debug_toolbar-1.png
deleted file mode 100644
index 737a495..0000000
--- a/platform/4.2/final/images/debug_toolbar-1.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/debug_toolbar-2.png b/platform/4.2/final/images/debug_toolbar-2.png
deleted file mode 100644
index e1d4f02..0000000
--- a/platform/4.2/final/images/debug_toolbar-2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/default_style.css b/platform/4.2/final/images/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.2/final/images/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.2/final/images/delete-project.png b/platform/4.2/final/images/delete-project.png
deleted file mode 100644
index d1eed79..0000000
--- a/platform/4.2/final/images/delete-project.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/detached-editor.png b/platform/4.2/final/images/detached-editor.png
deleted file mode 100644
index c8c1193..0000000
--- a/platform/4.2/final/images/detached-editor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/detail-formatters.png b/platform/4.2/final/images/detail-formatters.png
deleted file mode 100644
index 84b2dac..0000000
--- a/platform/4.2/final/images/detail-formatters.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/drag-sash.png b/platform/4.2/final/images/drag-sash.png
deleted file mode 100644
index 5b96132..0000000
--- a/platform/4.2/final/images/drag-sash.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/eedesc.png b/platform/4.2/final/images/eedesc.png
deleted file mode 100644
index 6de6cd7..0000000
--- a/platform/4.2/final/images/eedesc.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/enclosing-brackets.png b/platform/4.2/final/images/enclosing-brackets.png
deleted file mode 100644
index 707634e..0000000
--- a/platform/4.2/final/images/enclosing-brackets.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/errors-warnings-highlight.png b/platform/4.2/final/images/errors-warnings-highlight.png
deleted file mode 100644
index 751d0c2..0000000
--- a/platform/4.2/final/images/errors-warnings-highlight.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/event-bus.png b/platform/4.2/final/images/event-bus.png
deleted file mode 100644
index d1f3d0b..0000000
--- a/platform/4.2/final/images/event-bus.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/extensions_page.png b/platform/4.2/final/images/extensions_page.png
deleted file mode 100644
index 83a0ad8..0000000
--- a/platform/4.2/final/images/extensions_page.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/file-associations-page.png b/platform/4.2/final/images/file-associations-page.png
deleted file mode 100644
index 6c8994f..0000000
--- a/platform/4.2/final/images/file-associations-page.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/filters-in-cvs-syncview.png b/platform/4.2/final/images/filters-in-cvs-syncview.png
deleted file mode 100644
index 3052012..0000000
--- a/platform/4.2/final/images/filters-in-cvs-syncview.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/font-dialog-effects.png b/platform/4.2/final/images/font-dialog-effects.png
deleted file mode 100644
index c83732c..0000000
--- a/platform/4.2/final/images/font-dialog-effects.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/highlight.png b/platform/4.2/final/images/highlight.png
deleted file mode 100644
index daf180c..0000000
--- a/platform/4.2/final/images/highlight.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/icon.png b/platform/4.2/final/images/icon.png
deleted file mode 100644
index c07971b..0000000
--- a/platform/4.2/final/images/icon.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/ignore-warnings-source-folders.png b/platform/4.2/final/images/ignore-warnings-source-folders.png
deleted file mode 100644
index 3b43113..0000000
--- a/platform/4.2/final/images/ignore-warnings-source-folders.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/import-repo-pkg.png b/platform/4.2/final/images/import-repo-pkg.png
deleted file mode 100644
index 244e47f..0000000
--- a/platform/4.2/final/images/import-repo-pkg.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/import-repo-tps.png b/platform/4.2/final/images/import-repo-tps.png
deleted file mode 100644
index 05d34b0..0000000
--- a/platform/4.2/final/images/import-repo-tps.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/javadoc-hover-parameter-annotations.png b/platform/4.2/final/images/javadoc-hover-parameter-annotations.png
deleted file mode 100644
index 94368fd..0000000
--- a/platform/4.2/final/images/javadoc-hover-parameter-annotations.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/lcd-name-error.png b/platform/4.2/final/images/lcd-name-error.png
deleted file mode 100644
index a67989a..0000000
--- a/platform/4.2/final/images/lcd-name-error.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/lightweight_refresh_by_default.png b/platform/4.2/final/images/lightweight_refresh_by_default.png
deleted file mode 100644
index 17b1795..0000000
--- a/platform/4.2/final/images/lightweight_refresh_by_default.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/matching-bracket.png b/platform/4.2/final/images/matching-bracket.png
deleted file mode 100644
index 386ccd7..0000000
--- a/platform/4.2/final/images/matching-bracket.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/missing-nonnullbydefault-package.png b/platform/4.2/final/images/missing-nonnullbydefault-package.png
deleted file mode 100644
index 30a121c..0000000
--- a/platform/4.2/final/images/missing-nonnullbydefault-package.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/missing-nonnullbydefault-type.png b/platform/4.2/final/images/missing-nonnullbydefault-type.png
deleted file mode 100644
index b42bfb6..0000000
--- a/platform/4.2/final/images/missing-nonnullbydefault-type.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/mixvieweditor.png b/platform/4.2/final/images/mixvieweditor.png
deleted file mode 100644
index 7ffa20e..0000000
--- a/platform/4.2/final/images/mixvieweditor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/monitorexpression_tsk.gif b/platform/4.2/final/images/monitorexpression_tsk.gif
deleted file mode 100644
index 252d7eb..0000000
--- a/platform/4.2/final/images/monitorexpression_tsk.gif
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/multi-env-var.png b/platform/4.2/final/images/multi-env-var.png
deleted file mode 100644
index 9560711..0000000
--- a/platform/4.2/final/images/multi-env-var.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/new-null-analysis-message1.png b/platform/4.2/final/images/new-null-analysis-message1.png
deleted file mode 100644
index 69368c5..0000000
--- a/platform/4.2/final/images/new-null-analysis-message1.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/new-null-analysis-message2.png b/platform/4.2/final/images/new-null-analysis-message2.png
deleted file mode 100644
index 286f56d..0000000
--- a/platform/4.2/final/images/new-null-analysis-message2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/new-null-analysis-message3.png b/platform/4.2/final/images/new-null-analysis-message3.png
deleted file mode 100644
index 34d609a..0000000
--- a/platform/4.2/final/images/new-null-analysis-message3.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/newlook.png b/platform/4.2/final/images/newlook.png
deleted file mode 100644
index a620006..0000000
--- a/platform/4.2/final/images/newlook.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/nohighlight.png b/platform/4.2/final/images/nohighlight.png
deleted file mode 100644
index a57a7c2..0000000
--- a/platform/4.2/final/images/nohighlight.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/null-annotation-problems-redundant1.png b/platform/4.2/final/images/null-annotation-problems-redundant1.png
deleted file mode 100644
index 9af2519..0000000
--- a/platform/4.2/final/images/null-annotation-problems-redundant1.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/null-annotation-problems-redundant2.png b/platform/4.2/final/images/null-annotation-problems-redundant2.png
deleted file mode 100644
index df3dc72..0000000
--- a/platform/4.2/final/images/null-annotation-problems-redundant2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/null-annotation-problems1.png b/platform/4.2/final/images/null-annotation-problems1.png
deleted file mode 100644
index 9f344d8..0000000
--- a/platform/4.2/final/images/null-annotation-problems1.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/null-annotation-problems2.png b/platform/4.2/final/images/null-annotation-problems2.png
deleted file mode 100644
index 76b0c59..0000000
--- a/platform/4.2/final/images/null-annotation-problems2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/null-prefs.png b/platform/4.2/final/images/null-prefs.png
deleted file mode 100644
index d35fae8..0000000
--- a/platform/4.2/final/images/null-prefs.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/open-resource-show-in.png b/platform/4.2/final/images/open-resource-show-in.png
deleted file mode 100644
index c3762cc..0000000
--- a/platform/4.2/final/images/open-resource-show-in.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/os-less-unclosed-resource.png b/platform/4.2/final/images/os-less-unclosed-resource.png
deleted file mode 100644
index 525504a..0000000
--- a/platform/4.2/final/images/os-less-unclosed-resource.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/pde-wizard.png b/platform/4.2/final/images/pde-wizard.png
deleted file mode 100644
index bee9018..0000000
--- a/platform/4.2/final/images/pde-wizard.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/pot-resource-leak-example.png b/platform/4.2/final/images/pot-resource-leak-example.png
deleted file mode 100644
index 09d699c..0000000
--- a/platform/4.2/final/images/pot-resource-leak-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/quick-outline-camel-case.png b/platform/4.2/final/images/quick-outline-camel-case.png
deleted file mode 100644
index 602c182..0000000
--- a/platform/4.2/final/images/quick-outline-camel-case.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/resource-leak-default-warning.png b/platform/4.2/final/images/resource-leak-default-warning.png
deleted file mode 100644
index d7fd000..0000000
--- a/platform/4.2/final/images/resource-leak-default-warning.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/resource-leak-example.png b/platform/4.2/final/images/resource-leak-example.png
deleted file mode 100644
index d1b400e..0000000
--- a/platform/4.2/final/images/resource-leak-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/resource-leak-warnings.png b/platform/4.2/final/images/resource-leak-warnings.png
deleted file mode 100644
index 18110b7..0000000
--- a/platform/4.2/final/images/resource-leak-warnings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/searchbar.png b/platform/4.2/final/images/searchbar.png
deleted file mode 100644
index fcb7371..0000000
--- a/platform/4.2/final/images/searchbar.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/shared-area-polish.png b/platform/4.2/final/images/shared-area-polish.png
deleted file mode 100644
index 2497f11..0000000
--- a/platform/4.2/final/images/shared-area-polish.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/source-attachment-encoding.png b/platform/4.2/final/images/source-attachment-encoding.png
deleted file mode 100644
index 7537bff..0000000
--- a/platform/4.2/final/images/source-attachment-encoding.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/splitvieweditor.png b/platform/4.2/final/images/splitvieweditor.png
deleted file mode 100644
index 3bc8edd..0000000
--- a/platform/4.2/final/images/splitvieweditor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/stack-drag.png b/platform/4.2/final/images/stack-drag.png
deleted file mode 100644
index 590b477..0000000
--- a/platform/4.2/final/images/stack-drag.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/switch-case-enum.png b/platform/4.2/final/images/switch-case-enum.png
deleted file mode 100644
index f118691..0000000
--- a/platform/4.2/final/images/switch-case-enum.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/switch-missing-case-enum.png b/platform/4.2/final/images/switch-missing-case-enum.png
deleted file mode 100644
index c01f427..0000000
--- a/platform/4.2/final/images/switch-missing-case-enum.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/switch-missing-default.png b/platform/4.2/final/images/switch-missing-default.png
deleted file mode 100644
index 043239c..0000000
--- a/platform/4.2/final/images/switch-missing-default.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/switch-new-warnings.png b/platform/4.2/final/images/switch-new-warnings.png
deleted file mode 100644
index 079e423..0000000
--- a/platform/4.2/final/images/switch-new-warnings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/tab-navigation.png b/platform/4.2/final/images/tab-navigation.png
deleted file mode 100644
index 6628db3..0000000
--- a/platform/4.2/final/images/tab-navigation.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/tab-outline.png b/platform/4.2/final/images/tab-outline.png
deleted file mode 100644
index 26402fd..0000000
--- a/platform/4.2/final/images/tab-outline.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/tracing_page.png b/platform/4.2/final/images/tracing_page.png
deleted file mode 100644
index 648c7cc..0000000
--- a/platform/4.2/final/images/tracing_page.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/treecursor.png b/platform/4.2/final/images/treecursor.png
deleted file mode 100644
index 05d6577..0000000
--- a/platform/4.2/final/images/treecursor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/trim-styling.png b/platform/4.2/final/images/trim-styling.png
deleted file mode 100644
index 83e4cb4..0000000
--- a/platform/4.2/final/images/trim-styling.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/use-saturated-colors-off.png b/platform/4.2/final/images/use-saturated-colors-off.png
deleted file mode 100644
index 8803553..0000000
--- a/platform/4.2/final/images/use-saturated-colors-off.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/use-saturated-colors-on.png b/platform/4.2/final/images/use-saturated-colors-on.png
deleted file mode 100644
index ef2a11e..0000000
--- a/platform/4.2/final/images/use-saturated-colors-on.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/use-saturated-colors.png b/platform/4.2/final/images/use-saturated-colors.png
deleted file mode 100644
index e4e08e8..0000000
--- a/platform/4.2/final/images/use-saturated-colors.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/wrapped-os-less-unclosed-resource.png b/platform/4.2/final/images/wrapped-os-less-unclosed-resource.png
deleted file mode 100644
index 5138fe9..0000000
--- a/platform/4.2/final/images/wrapped-os-less-unclosed-resource.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/final/images/wrapped-resource.png b/platform/4.2/final/images/wrapped-resource.png
deleted file mode 100644
index 293b81b..0000000
--- a/platform/4.2/final/images/wrapped-resource.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.2/what-new-template/eclipse-whats-new-template.html b/platform/4.2/what-new-template/eclipse-whats-new-template.html
deleted file mode 100644
index 75cff43..0000000
--- a/platform/4.2/what-new-template/eclipse-whats-new-template.html
+++ /dev/null
@@ -1,198 +0,0 @@
-<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
-        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-  <style type="text/css">
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-.section {font-size: 20px; font-weight: bold;}
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-  </style>
-<title>Eclipse &quot;New and Noteworthy&quot; Template</title>
-</head>
-
-<body>
-<h1>Eclipse &quot;New and Noteworthy&quot; Template</h1>
-<p>Last revised 2012-06-27.</p>
-<p>This is the template for the &quot;New and Noteworthy&quot; document that
-  accompanies each Eclipse project milestone build.</p>
-<p>Note: This template document is XHTML 1.0 Transitional. Please use the W3C <a href="http://validator.w3.org/#validate_by_input">XHTML
-    Markup Validation Service</a> to check your document's markup before submitting.
-    This will detect screwed up HTML tags, images without an &quot;alt&quot;
-    attribute, and other tedious little details.</p>
-
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-  <li><a href="#Equinox">Equinox</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%" summary="news entries">
-
-  <tr>
-    <td id="Instructions" class="section" colspan="2">
-      <h2>Instructions</h2>
-    </td>
-  </tr>
-  
-  <tr id="item-name">
-    <td class="title">Item title, in sentence style, no trailing
-        punctuation, with unique id attribute on &lt;tr&gt;</td>
-    <td class="content">
-        A blurb pitched to the Eclipse community
-        (not just to members of the Eclipse Platform development team). Tell
-        end users about changes they'll see in the UI. Tell component writers
-        about changes they'll see at the client- and server-side APIs. Try to
-        generate some excitement; save the boring details for the manual; be short and don't repeat yourself. The
-        description should be complete sentences, with trailing punctuation.
-      <p>Use active voice (say "you", not "the user"), and follow other advice in the
-        <a href="http://wiki.eclipse.org/Eclipse_Doc_Style_Guide#topic-content">Topic&nbsp;Content</a>
-        section of the Eclipse Doc Style Guidelines.
-      </p>
-      <p>Stick to the default font and size. Make command names (<b>Quick Fix</b>),
-        keyboard shortcuts (<b>Ctrl+1</b>), and preference page paths
-        (<b>Preferences &gt; General &gt; Keys</b>) bold.
-      </p>
-      <p>Do <em>not</em> enclose the first paragraph of an item in <code>&lt;p&gt;&lt;/p&gt;</code> tags.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="screenshots">
-    <td class="title">Screenshots</td>
-    <td class="content">
-        If a small image sheds light, place it below the description, in a separate
-        paragraph. Regular screen snapshots should be done on Windows XP. Crop
-        out any extraneous stuff to focus the reader's attention on your new
-        feature. <span style="background-color: #FFFF00">The image should be
-        no more than 519 pixels wide and in PNG format</span> (as opposed
-        to GIF, TIF, BMP, or JPG). Use PNG-8 if your image doesn't have a lot of color,
-        or PNG-24 if the screen shot uses enough color to warrant additional color depth.
-        See also the 
-        <a href="http://wiki.eclipse.org/Eclipse_Doc_Style_Guide#graphics">Graphics</a>
-        section of the Eclipse Doc Style Guidelines.
-      <p>Microsoft Paint actually saves to PNG on Windows XP and can easily be
-        used to crop and save screenshots:</p>
-      <ul>
-        <li>Arrange the windows for the shot</li>
-        <li>Use the Print Screen key (or <b>Alt+Print Screen</b>) to capture the screen</li>
-        <li>Open Paint (under <b>All Programs &gt; Accessories</b>)</li>
-        <li><b>Ctrl+V</b> to paste</li>
-        <li>Select the area you want to keep</li>
-        <li><b>Ctrl+C</b> to copy it</li>
-        <li><b>Ctrl+N</b> to create a new canvas (ok to discard old one)</li>
-        <li><b>Ctrl+V</b> to paste selected portion</li>
-        <li><b>Save As &gt; PNG</b></li>
-      </ul>
-      <p>Name the file is a way that is appropriate and specific to the item
-        (e.g., key-bindings.png, rather than something generic like image.png).
-        Use all <b>lowercase</b> letters in the image file name, including the &quot;.png&quot; 
-        file extension. As a separator, use hyphen &quot;-&quot; rather than
-        underscore 
-        &quot;_&quot;. </p>
-      <p>Put all the images in a sibling directory named &quot;images&quot;.
-        This gives XHTML like:<br/>
-        <code>&lt;img src=&quot;images/foo-view.png&quot; alt=&quot;The Foo View&quot;/&gt;</code><br/>
-        Include a suitable <a href="http://www.w3.org/TR/html4/struct/objects.html#h-13.8"><code>alt</code></a> attribute
-        (which is mandatory in XHTML 1.0). Do not embed the width and height of the image.</p>
-      <p>If the <code>alt</code> attribute text cannot sufficiently replace the image contents
-        (e.g. for a screenshot that shows source code), then enclose the img element in a link
-        to a plain &quot;.txt&quot; file with the same name as the image:<br/>
-        <code>&lt;a href=&quot;images/foo-view.txt&quot;&gt;&lt;img ...</code></p>
-      <p>The images should be left-justified (as opposed to centered). </p>
-      <p>Use the W3C <a href="http://validator.w3.org/#validate_by_input">XHTML
-          Markup Validation Service</a> to check your document's markup before
-          submitting.</p></td>
-  </tr>
-  
-  <tr>
-    <td id="Platform" class="section" colspan="2">
-      <h2>Platform</h2>
-    </td>
-  </tr>
-  
-  <tr id="first-item">
-    <td class="title">First item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-  
-  <tr id="second-item">
-    <td class="title">Second item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-
-
-  <tr>
-    <td id="JDT" class="section" colspan="2">
-      <h2>JDT</h2>
-    </td>
-  </tr>
-  
-  <tr id="first-jdt-item">
-    <td class="title">First item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-
-
-  <tr>
-    <td id="PDE" class="section" colspan="2">
-      <h2>PDE</h2>
-    </td>
-  </tr>
-  
-  <tr id="first-pde-item">
-    <td class="title">First item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-
-
-  <tr>
-    <td id="Equinox" class="section" colspan="2">
-      <h2>Equinox</h2>
-    </td>
-  </tr>
-  
-  <tr id="first-equinox-item">
-    <td class="title">First item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-
-
-  <tr>
-    <td colspan="2"/>
-  </tr>
-  
-</table>
-</body>
-</html>
diff --git a/platform/4.2/what-new-template/eclipse-whats-new-template.zip b/platform/4.2/what-new-template/eclipse-whats-new-template.zip
deleted file mode 100644
index 4e61940..0000000
--- a/platform/4.2/what-new-template/eclipse-whats-new-template.zip
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M1/eclipse-news-M1.html b/platform/4.3/M1/eclipse-news-M1.html
deleted file mode 100644
index d334c6a..0000000
--- a/platform/4.3/M1/eclipse-news-M1.html
+++ /dev/null
@@ -1,145 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<style type="text/css">
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Project 4.3 M1 News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.3 M1 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M1 
-  (August 10, 2012) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  <tr id="ua-lucene">
-    <td class="title">Migrated to Lucene 3.5</td>
-    <td class="content">
-      The Eclipse platform help system has migrated from Lucene 2.9.1 to Lucene 3.5.
-      This change brings improved performance and many bug fixes in help search.
-      Some old help system API related to Lucene has been changed or removed as part
-      of this fix. Refer to the platform 4.3 migration guide for more details.
-    </td>
-  </tr>
-
-
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr id="convert-if-else-to-switch">
-    <td class="title">New 'Convert if-else to switch' quick assist</td>
-    <td class="content">
-      The new <b>Convert 'if-else' to 'switch'</b> quick assist (<b>Ctrl+1</b>) allows you to convert an if-else statement to 
-      an equivalent switch statement.
-      <p><img src="images/convert-if-else-to-switch.png" alt=""/></p>
-      
-      This quick assist is the reverse of the existing <b>Convert 'switch' to 'if-else'</b> quick assist.
-    </td>
-  </tr>
-  <tr id="tolerateIllegalAmbiguousVarargsInvocation">
-    <td class="title">Force Eclipse to compile (illegal) ambiguous varargs code</td>
-    <td class="content"> JDK 6 and below had a bug and considered the code below legal.
-	However, this bug was fixed in JDK 7 and the code now reports an ambiguous invocation error at the call site for test(..).
-	Eclipse Juno followed and fixed this across all compliance levels.
-	<p><a href="images/illegal-ambiguous-varargs-error.txt"><img src="images/illegal-ambiguous-varargs-error.png" alt="follow link for source"/></a></p>
-	<p>If you still want the above code to compile in compliance &lt; 1.7, to mimic JDK 6 or below, you can use the
-	system property <b>tolerateIllegalAmbiguousVarargsInvocation</b> to force Eclipse to tolerate such ambiguous varargs cases.
-	This property can e.g. be set in the eclipse.ini file after the -vmargs setting:</p>
-	<pre><code>...
--vmargs
--DtolerateIllegalAmbiguousVarargsInvocation=true
-...</code></pre>
-	<p><i>Note</i>: With this setting, Eclipse also	mimics JDK 6 and below in raising an error in other cases that are legal in both JDK 7 and Eclipse:</p>
-	<p><a href="images/illegal-ambiguous-varargs-error2.txt"><img src="images/illegal-ambiguous-varargs-error2.png" alt="follow link for source"/></a></p>
-	
-	</td>
-  </tr>
-  <tr id="new-batch-compiler-options">
-    <td class="title">New batch compiler options</td>
-    <td class="content"> If you use the ECJ batch compiler using the command line or Ant tasks, you can now configure the following options which previously could only be set through
-	the <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings</b> page:
-	<ul>
-      <li>invalidJavadoc: set all warnings for malformed Javadoc tags</li>
-      <li>invalidJavadocTag: validate Javadoc tag arguments</li>
-      <li>invalidJavadocTagDep: validate deprecated references in Javadoc tag args</li>
-      <li>invalidJavadocTagNotVisible: validate non-visible references in Javadoc tag args</li>
-      <li>invalidJavadocVisibility(&lt;visibility&gt;): specify visibility modifier for malformed Javadoc tag warnings</li>
-      <li>missingJavadocTags: enable detection of missing Javadoc tags</li>
-      <li>missingJavadocTagsOverriding: detect missing Javadoc tags in overriding methods</li>
-      <li>missingJavadocTagsMethod: detect missing Javadoc tags for method type parameter</li>
-      <li>missingJavadocTagsVisibility(&lt;visibility&gt;): specify visibility modifier for missing Javadoc tags warnings</li>
-      <li>missingJavadocComments: detect missing Javadoc comments</li>
-      <li>missingJavadocCommentsOverriding: detect missing Javadoc tags in overriding methods</li>
-      <li>missingJavadocCommentsVisibility(&lt;visibility&gt;): specify visibility modifier for missing Javadoc comments warnings</li>
-      <li>nullAnnotConflict: detect conflict between null annotation specified and nullness inferred. Is effective only with nullAnnot option enabled</li>
-      <li>nullAnnotRedundant: detect redundant specification of null annotation. Is effective only with nullAnnot option enabled</li>
-      <li>nullUncheckedConversion: detect unchecked conversion from non-annotated type to @NonNull type. Is effective only with nullAnnot option enabled</li>
-      <li>unusedParam: detect unused parameter</li>
-      <li>unusedParamOverriding: detect unused parameter for overriding method</li>
-      <li>unusedParamImplementing: detect unused parameter for implementing method</li>
-      <li>unusedParamIncludeDoc: detect unused parameter documented in comment tag</li>
-      <li>unusedThrownWhenOverriding: detect unused declared thrown exception in overriding method</li>
-      <li>unusedThrownIncludeDocComment: detect unused declared thrown exception, documented in a comment tag</li>
-      <li>unusedThrownExemptExceptionThrowable: detect unused declared thrown exception, exempt Exception and Throwable</li>
-	</ul>
-	<p> For more information on using batch compiler options, please refer to <b>Help &gt; Java Development User Guide &gt; Tasks &gt; Compiling Java Code &gt; Using the batch compiler</b>.</p>
-    </td>
-  </tr>
-  <tr id="content-assist-TL_CONSTRUCTOR_START">
-    <td class="title">New API to indicate content assist requested on the start of a constructor</td>
-    <td class="content">
-      org.eclipse.jdt.core.CompletionContext.TL_CONSTRUCTOR_START:
-      <pre>
-	  /**
-	   * The completed token is the first token of a constructor
-	   * invocation expression.
-	   * e.g.
-	   * 
-	   * public class X {
-	   *   public void bar() {
-	   *     new Foo| // completion occurs at |
-	   *   }
-	   * }
-	   */
-	</pre>
-    </td>
-  </tr>
-
-
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-</body>
-</html>
diff --git a/platform/4.3/M1/images/convert-if-else-to-switch.png b/platform/4.3/M1/images/convert-if-else-to-switch.png
deleted file mode 100644
index be3ea31..0000000
--- a/platform/4.3/M1/images/convert-if-else-to-switch.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M1/images/illegal-ambiguous-varargs-error-Juno.png b/platform/4.3/M1/images/illegal-ambiguous-varargs-error-Juno.png
deleted file mode 100644
index 5d4aac9..0000000
--- a/platform/4.3/M1/images/illegal-ambiguous-varargs-error-Juno.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M1/images/illegal-ambiguous-varargs-error.png b/platform/4.3/M1/images/illegal-ambiguous-varargs-error.png
deleted file mode 100644
index 22290a0..0000000
--- a/platform/4.3/M1/images/illegal-ambiguous-varargs-error.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M1/images/illegal-ambiguous-varargs-error.txt b/platform/4.3/M1/images/illegal-ambiguous-varargs-error.txt
deleted file mode 100644
index 9630ec5..0000000
--- a/platform/4.3/M1/images/illegal-ambiguous-varargs-error.txt
+++ /dev/null
@@ -1,11 +0,0 @@
-    public static void test(int... a) {
-        System.out.println(Arrays.toString(a));
-    }
-    
-    public static void test(Object... a) {
-        System.out.println(Arrays.toString(a));
-    }
-    
-    public static void main(String[] args) {
-        test(1); // 'test' flagged ambiguous
-    }
diff --git a/platform/4.3/M1/images/illegal-ambiguous-varargs-error2.png b/platform/4.3/M1/images/illegal-ambiguous-varargs-error2.png
deleted file mode 100644
index 27f715e..0000000
--- a/platform/4.3/M1/images/illegal-ambiguous-varargs-error2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M1/images/illegal-ambiguous-varargs-error2.txt b/platform/4.3/M1/images/illegal-ambiguous-varargs-error2.txt
deleted file mode 100644
index 4a990bd..0000000
--- a/platform/4.3/M1/images/illegal-ambiguous-varargs-error2.txt
+++ /dev/null
@@ -1,6 +0,0 @@
-    public static void foo(int... i) { }
-    public static void foo(double... d) { }
-    
-    public static void main(String[] args) {
-        foo(1, 2, 3); // foo flagged ambiguous
-    }
diff --git a/platform/4.3/M2/default_style.css b/platform/4.3/M2/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.3/M2/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.3/M2/eclipse-news-M2.html b/platform/4.3/M2/eclipse-news-M2.html
deleted file mode 100644
index fcadebe..0000000
--- a/platform/4.3/M2/eclipse-news-M2.html
+++ /dev/null
@@ -1,112 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Project 4.3 M2 News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.3 M2 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M2 
-  (September 21, 2012) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  
-  <tr id="detached-sash">
-    <td class="title">Detached windows with sash</td>
-    <td class="content">
-      When you detach a view or editor into its own separate window, it now
-      has all the capabilities of a normal workbench window. They now support multiple stacks of
-      views separated by sashes with arbitrary layouts. The detached parts will remain synchronized
-      with the master window that they were detached from. This is especially handy for people developing
-      with two or more monitors, so they can spread views across several monitors and keep them synchronized.
-		<p><img src="images/detached-sash.png" alt="Detached window with multiple views separated by sash."/></p>
-    </td>
-  </tr>
-
-  <tr id="trim-drag">
-    <td class="title">Trim dragging</td>
-    <td class="content">
-      You can now drag toolbars to reposition them. 
-      <p><img src="images/trim-drag.png" alt="Dragging a toolbar."/></p>
-      <p>The perspective switcher can also be dragged to the left or right of the window and it will switch to a 
-        vertical orientation.</p>
-	  <p><img src="images/vertical-switcher.png" alt="Dragging perspective switcher to vertical orientation."/></p>
-    </td>
-  </tr>
-
-  <tr id="import-nested">
-    <td class="title">Import nested projects</td>
-    <td class="content">
-      The <b>Import Projects</b> wizard now has an option to continue searching for projects to import
-      recursively within any project it finds. This allows you to import physically nested projects
-      at the same time.
-      <p><img src="images/import-nested.png" alt="Import nested projects."/></p>
-    </td>
-  </tr>
-
-  <tr id="ant184">
-    <td class="title">Platform updated to Ant 1.8.4</td>
-    <td class="content">
-      The platform has been updated to use Apache Ant version 1.8.4. To see what is new in version 1.8.4 you can
-      check the <a href="http://apache.mirrors.tds.net//ant/README.html">Apache Ant what's new</a>.
-    </td>
-  </tr>
-  
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr id="content-assist-additional-info-in-debug-views">
-    <td class="title">Content assist shows Javadoc in Display, Expressions and Variables view</td>
-    <td class="content">
-        Content assist in the Display, Expressions and Variables view now shows Javadoc:
-		<p><img src="images/additional-info.png" alt="Screenshot showing Javadoc when doing content assist"/></p>
-	</td>
-  </tr>
-  
-  
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  
-  <tr id="ee-desc-feature">
-    <td class="title">New API Tools EE descriptions feature</td>
-    <td class="content">
-      The API Tools Execution Environment descriptions are now supplied on the Eclipse update sites as a single
-      installable feature.  The feature includes the descriptions for all supported execution environments.
-      
-       <p><img src="images/eedescfeature.png" alt="New EE Desc feature on update sites"/></p> 
-    </td>
-  </tr>
-  
-  <tr id="improved-feature-selection">
-    <td class="title">Improved feature selection dialog</td>
-    <td class="content">
-      The feature selection dialog used in wizards and editors has been enhanced with better wildcard support
-      and filtering options.
-      
-       <p><img src="images/featureselection.png" alt="Improved feature selection dialog"/></p> 
-    </td>
-  </tr>
-  
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Kepler milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M1-201208101300/news/">New for Eclipse Kepler milestone build M1 (August 10, 2012)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.3/M2/images/additional-info.png b/platform/4.3/M2/images/additional-info.png
deleted file mode 100644
index c8b741b..0000000
--- a/platform/4.3/M2/images/additional-info.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M2/images/detached-sash.png b/platform/4.3/M2/images/detached-sash.png
deleted file mode 100644
index 2b6e820..0000000
--- a/platform/4.3/M2/images/detached-sash.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M2/images/eedescfeature.png b/platform/4.3/M2/images/eedescfeature.png
deleted file mode 100644
index fe8e9f1..0000000
--- a/platform/4.3/M2/images/eedescfeature.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M2/images/featureselection.png b/platform/4.3/M2/images/featureselection.png
deleted file mode 100644
index cf9dc8c..0000000
--- a/platform/4.3/M2/images/featureselection.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M2/images/import-nested.png b/platform/4.3/M2/images/import-nested.png
deleted file mode 100644
index 271a2ad..0000000
--- a/platform/4.3/M2/images/import-nested.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M2/images/trim-drag.png b/platform/4.3/M2/images/trim-drag.png
deleted file mode 100644
index 9c79b41..0000000
--- a/platform/4.3/M2/images/trim-drag.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M2/images/vertical-switcher.png b/platform/4.3/M2/images/vertical-switcher.png
deleted file mode 100644
index 8798efa..0000000
--- a/platform/4.3/M2/images/vertical-switcher.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M3/default_style.css b/platform/4.3/M3/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.3/M3/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.3/M3/eclipse-news-M3.html b/platform/4.3/M3/eclipse-news-M3.html
deleted file mode 100644
index 26720b1..0000000
--- a/platform/4.3/M3/eclipse-news-M3.html
+++ /dev/null
@@ -1,178 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Project 4.3 M3 News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.3 M3 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M3 
-  (November 2, 2012) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  <tr id="x-start-on-first-thread">
-    <td class="title">Option to omit -XstartOnFirstThread</td>
-    <td class="content">
-      If you are launching an SWT program on Mac OS X, you can now selectively add / remove the <code>-XstartOnFirstThread</code> VM argument
-      in the event your VM does not support it. This option can be configured per launch configuration and is available on the standard Arguments
-      tab for Java configurations (Java Application, Eclipse, etc.).
-      <p><img src="images/x-start-on-first-thread.png" alt="New VM preference allowing users to selectively add the -XstartOnFirstThread argument per-configuration"/></p>
-    </td>
-  </tr>
-  <tr id="only-include-exported-entries">
-    <td class="title">Global preference to include exported entries during launching</td>
-    <td class="content">
-      A new global preference has been added so you can only allow exported classpath entries to be used during launching. Previously, this 
-      was only customizable per launch configuration on the default classpath entry on the Java Classpath tab. The new preference does not affect 
-      launch configuration data, so no migration is needed.
-      
-      <p>
-      The new preference can be found on the <b>Java &gt; Debug</b> preference page.
-      <p><img src="images/only-include-exported.png" alt="New global preference to only include exported classpath entries"/></p>
-      </p>
-    </td>
-  </tr>
-  <tr id="launch-dialog-warnings">
-    <td class="title">Launch configuration dialog can show warnings</td>
-    <td class="content">
-      Previously, contributors could only set an 'ok' or an 'error' state in their launch configuration tags / groups. Now,
-      contributors can set a warning state with a message for their tabs / groups - possibly warning users about set options
-      that might be problematic, but do not necessarily need to prevent launching.
-      <p><img src="images/lcd-warnings.png" alt="Launch configuration dialog showing warning message / state"/></p>
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr id="javadoc-view-target">
-    <td class="title">Javadoc view resolves enclosing method call and keeps last target</td>
-    <td class="content">
-      The <b>Javadoc</b> and <b>Declaration</b> views now try to find the enclosing method call
-      if the selection or caret position doesn't resolve to a valid Java element.
-      <p>
-        <img src="images/javadoc-view-target.png" alt="'String.copyValueOf(data, offset, count)', with 'data' selected."/>
-      </p>
-      Furthermore, they keep the last resolved target element even if no new target can be resolved.
-    </td>
-  </tr>
-  
-  <tr id="unused-type-parameter">
-    <td class="title">Detection of unused type parameters</td>
-    <td class="content">
-      The compiler can now detect unused type parameters:
-      <p>
-        <img src="images/unused-type-parameter.png" alt=""/>
-      </p>
-      <p>
-        The <b>Unused type parameter</b> diagnostic is set to Ignore by default and can be enabled on the 
-		<b>Java &gt; Compiler &gt; Errors/Warnings</b>
-		preference page.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="unused-type-parameter">
-    <td class="title">Option to omit @Override for interface methods</td>
-    <td class="content">
-      Eclipse can add <code>@Override</code> annotations for overriding methods:
-      <p>
-        <img src="images/override-annotation-code-style.png" alt="Code Style preference page"/>
-      </p>
-      <p>
-        If your code uses Java 1.6 or higher, the <code>@Override</code> annotation is also added to
-        methods that override an interface method. If you don't want to use <code>@Override</code>
-        in this case, then follow the link and disable the corresponding compiler option:
-      </p>
-      <p>
-        <img src="images/override-annotation-compiler.png" alt="Errors/Warnings preference page, checkbox 'Include implementations of interface methods (1.6 or higher)'"/>
-      </p>
-      <p>
-        You may also want to enable the diagnostic for Missing '@Override' annotation.   
-      </p>
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  
-  <tr id="additional-type-info">
-    <td class="title">Javadoc hover available in plug-in manifest editor</td>
-    <td class="content">
-      When editing the plugin.xml or manifest.mf files using the <b>Plug-in Manifest Editor</b>, 
-      opening content assist for type proposals will now display additional javadoc information.
-      <p>
-        <img src="images/additional-type-info.png" alt="Additional info javadoc hover for type proposals"/>
-      </p>
-    </td>
-  </tr>
-  
-    <tr id="plugin-image-view">
-    <td class="title">Plug-in image browser view</td>
-    <td class="content">
-      A new view has been added to PDE.  The <b>Plug-in Image Browser</b> view displays icons and other
-      images from your target platform, running application or current workspace. 
-      <p>
-      	When an image is selected, additional information is displayed at the bottom of the view.  The
-        reference text can be used in plug-in extensions to refer to images in other bundles.
-      </p>
-      <p>
-        <img src="images/plugin-image-view.png" alt="The plug-in image browser view"/>
-      </p>
-    </td>
-  </tr>
-  
-    <tr id="default-launch-ee">
-    <td class="title">Launch configurations choose default execution environment</td>
-    <td class="content">
-      New PDE launch configurations (Eclipse Application, JUnit Plug-in Test, OSGi Framework) will
-      use a default execution environment to determine which Java runtime environment to launch with.
-      The launch configuration can be changed to use a different execution environment or a specific
-      JRE on the <b>Main</b> tab.
-      <p>
-        To find a valid execution environment, all known environments are checked against each bundle 
-        or plug-in that will be launched. Only an execution environment that is valid for all
-        plug-ins and bundles will be selected.  If no valid environment is found, a default JRE
-        will be chosen as before.
-      </p>
-      <p>
-        <img src="images/default-launch-ee.png" alt="Java runtime settings on the Main tab of PDE launch configurations"/>
-      </p>
-      <p>
-      	The JRE associated with the selected execution environment will be used to launch. To change 
-      	which JRE is associated with an execution environment, use the <b>Preferences > Java > Installed JREs > 
-      	Execution Environments</b> preference page.
-      </p>
-    </td>
-  </tr>
-    <tr id="pde-5-bree">
-    <td class="title">PDE UI requires a 1.5 EE</td>
-    <td class="content">
-      The bundle required execution environment for the PDE UI bundles org.eclipse.pde.core and
-      org.eclipse.pde.ui is now J2SE-1.5.
-    </td>
-  </tr>
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Kepler milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M2-201209201300/news/">New for Eclipse Kepler milestone build M2 (September 21, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M1-201208101300/news/">New for Eclipse Kepler milestone build M1 (August 10, 2012)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.3/M3/images/additional-type-info.png b/platform/4.3/M3/images/additional-type-info.png
deleted file mode 100644
index 3f24504..0000000
--- a/platform/4.3/M3/images/additional-type-info.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M3/images/default-launch-ee.png b/platform/4.3/M3/images/default-launch-ee.png
deleted file mode 100644
index 2b327f5..0000000
--- a/platform/4.3/M3/images/default-launch-ee.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M3/images/javadoc-view-target.png b/platform/4.3/M3/images/javadoc-view-target.png
deleted file mode 100644
index 25305da..0000000
--- a/platform/4.3/M3/images/javadoc-view-target.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M3/images/lcd-warnings.png b/platform/4.3/M3/images/lcd-warnings.png
deleted file mode 100644
index 2ade3b5..0000000
--- a/platform/4.3/M3/images/lcd-warnings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M3/images/only-include-exported.png b/platform/4.3/M3/images/only-include-exported.png
deleted file mode 100644
index e6cacc2..0000000
--- a/platform/4.3/M3/images/only-include-exported.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M3/images/override-annotation-code-style.png b/platform/4.3/M3/images/override-annotation-code-style.png
deleted file mode 100644
index 6da2b0a..0000000
--- a/platform/4.3/M3/images/override-annotation-code-style.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M3/images/override-annotation-compiler.png b/platform/4.3/M3/images/override-annotation-compiler.png
deleted file mode 100644
index 3b0516c..0000000
--- a/platform/4.3/M3/images/override-annotation-compiler.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M3/images/plugin-image-view.png b/platform/4.3/M3/images/plugin-image-view.png
deleted file mode 100644
index bf7815d..0000000
--- a/platform/4.3/M3/images/plugin-image-view.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M3/images/unused-type-parameter.png b/platform/4.3/M3/images/unused-type-parameter.png
deleted file mode 100644
index 0e6df20..0000000
--- a/platform/4.3/M3/images/unused-type-parameter.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M3/images/x-start-on-first-thread.png b/platform/4.3/M3/images/x-start-on-first-thread.png
deleted file mode 100644
index 76ecce0..0000000
--- a/platform/4.3/M3/images/x-start-on-first-thread.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M4/default_style.css b/platform/4.3/M4/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.3/M4/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.3/M4/eclipse-news-M4.html b/platform/4.3/M4/eclipse-news-M4.html
deleted file mode 100644
index caf3116..0000000
--- a/platform/4.3/M4/eclipse-news-M4.html
+++ /dev/null
@@ -1,174 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Project 4.3 M4 News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.3 M4 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M4 
-  (December 14, 2012) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  
-  <tr id="performance">
-    <td class="title">Performance enhancements</td>
-    <td class="content">
-      Significant performance enhancements have been made in the Platform user interface in this milestone. In particular, some applications
-      that were experiencing slow editor opening, closing, and switching are now much faster. Editor selection changes and the <b>Open Resource</b>
-      dialog have also been made faster. A number of leaks have been addressed to avoid long-running applications don't run out of memory.
-      <p><img src="images/speed.jpg" alt="Speedometer"><br>
-	  <small>Photographer: YtseJam Photography / Creative Commons Attribution 2.0</small>
-	  </p>
-	</td>
-  </tr>
-
-  <tr id="gtk3">
-    <td class="title">SWT for GTK3</td>
-    <td class="content">
-      32-bit and 64-bit GTK3 have joined the lineup of supported configurations for which SWT and Eclipse are routinely built. This implementation is currently early access. Everyone is encouraged to download and test these new builds, and to log bugs in <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform">bugzilla</a>.
-      <p>Note to load the SWT GTK3 libraries, you must set an environment variable SWT_GTK3 prior to starting Eclipse. (ex. export SWT_GTK3=1)</p>
-      <p><img src="images/gtk3.png" alt="GTK3 Control Example"></p>  
-	</td>
-  </tr>
-
-  <tr id="ant-augment">
-    <td class="title">Support for the Ant augment task</td>
-    <td class="content">
-      The Ant editor now has support for the Ant augment task. More information about the augment task can be found on the Apache help site 
-      <a href="http://ant.apache.org/manual/Tasks/augment.html">here</a>. 
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  
-  <tr id="stacktrace-paste">
-    <td class="title">Paste direct to a new stacktrace console</td>
-    <td class="content">
-      Previously, when creating a new Java stacktrace console, you would have to select and delete the default text prompting you to paste
-      a stacktrace. In 4.3M4 you can simply paste the stacktrace in and the default text will be auto-deleted for you.
-    </td>
-  </tr>
-
-  <tr id="xml-dom-structure">
-    <td class="title">XML DOM logical structures</td>
-    <td class="content">
-      JDT now provides a default logical structure for XML DOMs, which can be used during debugging to view the children and attributes of a node as simple arrays.
-      <p>
-      <img src="images/dom-structure.png" alt="Variables view showing the XML DOM logical structure"/>
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="combine-strings">
-    <td class="title">Quick assist to combine Strings</td>
-    <td class="content">
-      The new <b>Combine to single String</b> quick assist (<b>Ctrl+1</b>) replaces String concatenations
-      with a single String literal. 
-      <p>
-        <img src="images/combine-strings.png" alt="String s = &quot;Delete &quot; + &quot;two&quot; + &quot; files?&quot; // becomes: String s = &quot;Delete two files?&quot;"/>
-      </p>
-    </td>
-  </tr>
-  
-    <tr id="inherit-null-annotations">
-    <td class="title">Option to inherit null annotations</td>
-    <td class="content">
-        JDT has a new option controlling how to interpret null annotations in the presence of inheritance.
-        This should facilitate the migration towards null annotations in projects with
-        mixed code ownership.
-      <p>For the sake of code readability, JDT expects null annotations of an overridden
-        method to be repeated in overriding methods. In the following example the analysis
-        normally complains that <code>arg</code> is not annotated in <code>ClientClass</code>,
-        which means, this class doesn't formally conform to the contract of its super-interface.
-      </p>
-      <p><img title="Example for inheritance of null annotations" src="images/inherit-null-annotations-example.png"/></p>
-      <p>Starting with 4.3M4 this behavior can be changed by selecting the option
-        <strong>Inherit null annotations</strong>.
-      </p>
-      <p><img title="Option for inheritance of null annotations" src="images/inherit-null-annotations-option.png"/></p>
-      <p>In this new mode the analysis implicitly fills in all missing annotations
-        in overriding methods and uses the annotations from the overridden method.
-        In the above example the error will go away, and analysis concludes that the
-        code is actually safe, which is likely when the contract had already been
-        defined in the javadoc comment and the implementor actually adheres to that
-        contract. If, on the other hand, the implementation does not comply with the
-        inherited specification, new errors will be reported as shown below.
-      </p>
-      <p><img title="Negative example for inheritance of null annotations" src="images/inherit-null-annotations-example2.png"/></p>
-      <p>If inheritance of null annotations encounters any ambiguity or conflict
-        the analysis falls back to requiring explicit annotations.
-      </p>
-    </td>
-  </tr>
-
-  <tr id="close-quietly">
-    <td class="title">Leak analysis respects well-known utilities</td>
-    <td class="content">
-        JDT's analysis for resource leaks has been made aware of well known utilities
-        from google and apache libraries.
-      <p>Generally, this analysis looks for <code>close()</code> method calls
-        directly on a resource (any value of type <code>Closeable</code>).
-        However, in order to reduce boilerplate exception handling, several libraries
-        are providing methods like <code>closeQuietly(Closeable)</code>.
-        Previously, the analysis would complain about the missing call to <code>close()</code>
-        as shown below:
-      </p>
-      <p><img title="Example for close quietly" src="images/close-quietly-example.png"/></p>
-      <p>This warning is not relevant and will no longer be reported.
-        To achieve this, JDT now hardcodes a (short) white list of functions that
-        are known to safely close a given resource.
-      </p>
-    </td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-
-  <tr id="import-package">
-    <td class="title">New import package quick fixes</td>
-    <td class="content">
-      New quick fixes are available when you have an unresolved type in a Java file.  If the unresolved type
-      can be found in a package exported by a plug-in, a quick fix will be available to add an import
-      package entry to your plug-in manifest.  There is also a quick fix to add the exporting plug-in to
-      your manifest's require bundle header.
-      <p>
-      <img src="images/import-package.png" alt="Import package quick fix on an unresolved type"/>
-      </p>
-      <p>
-      If a package providing the type is available but the package is not exported by its plug-in, a quick fix will
-      offer to fix the providing plug-in's manifest. Only plug-ins in the workspace can be modified this
-      way.
-      </p>
-      <p>
-      <img src="images/export-package.png" alt="Export package quick fix on an unresolved type that is not exported"/>
-      </p>
-    </td>
-  </tr>
-
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Kepler milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M3-201210312000/news/">New for Eclipse Kepler milestone build M3 (November 2, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M2-201209201300/news/">New for Eclipse Kepler milestone build M2 (September 21, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M1-201208101300/news/">New for Eclipse Kepler milestone build M1 (August 10, 2012)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.3/M4/images/close-quietly-example.png b/platform/4.3/M4/images/close-quietly-example.png
deleted file mode 100644
index 6c29f05..0000000
--- a/platform/4.3/M4/images/close-quietly-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M4/images/combine-strings.png b/platform/4.3/M4/images/combine-strings.png
deleted file mode 100644
index 95a65f3..0000000
--- a/platform/4.3/M4/images/combine-strings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M4/images/dom-structure.png b/platform/4.3/M4/images/dom-structure.png
deleted file mode 100644
index dc19e15..0000000
--- a/platform/4.3/M4/images/dom-structure.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M4/images/export-package.png b/platform/4.3/M4/images/export-package.png
deleted file mode 100644
index ec50bb7..0000000
--- a/platform/4.3/M4/images/export-package.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M4/images/gtk3.png b/platform/4.3/M4/images/gtk3.png
deleted file mode 100644
index a9468b4..0000000
--- a/platform/4.3/M4/images/gtk3.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M4/images/import-package.png b/platform/4.3/M4/images/import-package.png
deleted file mode 100644
index 7d13527..0000000
--- a/platform/4.3/M4/images/import-package.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M4/images/inherit-null-annotations-example.png b/platform/4.3/M4/images/inherit-null-annotations-example.png
deleted file mode 100644
index a51a9da..0000000
--- a/platform/4.3/M4/images/inherit-null-annotations-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M4/images/inherit-null-annotations-example2.png b/platform/4.3/M4/images/inherit-null-annotations-example2.png
deleted file mode 100644
index 5f41dd9..0000000
--- a/platform/4.3/M4/images/inherit-null-annotations-example2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M4/images/inherit-null-annotations-option.png b/platform/4.3/M4/images/inherit-null-annotations-option.png
deleted file mode 100644
index 322f055..0000000
--- a/platform/4.3/M4/images/inherit-null-annotations-option.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M4/images/speed.jpg b/platform/4.3/M4/images/speed.jpg
deleted file mode 100644
index f42c47e..0000000
--- a/platform/4.3/M4/images/speed.jpg
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M5/default_style.css b/platform/4.3/M5/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.3/M5/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.3/M5/eclipse-news-M5.html b/platform/4.3/M5/eclipse-news-M5.html
deleted file mode 100644
index 71b2405..0000000
--- a/platform/4.3/M5/eclipse-news-M5.html
+++ /dev/null
@@ -1,189 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Project 4.3 M5 News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.3 M5 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M5 
-  (February 1, 2013) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-</p>
-<ul>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-  <li><a href="#Platform">Platform</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr id="null-annotations-for-fields">
-    <td class="title">Null annotations for fields</td>
-    <td class="content">
-      The annotation-based null analysis &mdash; first released with Eclipse Indigo &mdash; has been extended
-      to apply also to fields. If enabled, this analysis will now detect the following problems
-      concerning any field annotated with <code>@NonNull</code>:
-      <ul>
-      <li>If the field is not properly initialized to a non-null value.</li>
-      <li>If a value is assigned to the field that is not known to be non-null.</li>
-      </ul>
-      <p>In return to these obligations, dereferencing a <code>@NonNull</code> field is regarded as always safe.
-      </p>
-      <p>If a field is marked as <code>@Nullable</code>, generally every direct dereference
-      	of the field is flagged as a potential null pointer access. Even a null check for such a field is not
-      	a perfect protection due to dangers of side effects, effects via aliased references, and concurrency.</p>
-      <p>As a compromise between safety and convenience, the compiler can be configured to apply
-      	<strong>"syntactic null analysis for fields"</strong>.
-      	With this option enabled, the compiler syntactically recognizes
-      	a narrow range of code patterns where a null-check of a field is <em>directly</em> followed by
-      	a dereference or an assignment to a <code>@NonNull</code> variable. For these particular situations,
-      	no problem will be reported.</p>
-      <p>In the following example, the check in line 12 properly protects the access in line 13, whereas
-      	the knowledge that field <code>nullable</code> holds a non-null value (in line 15) is spoiled by
-      	the intermediate statement in line 16.</p>
-	  <p><a href="images/null-annotations-for-fields-examples.txt"><img src="images/null-annotations-for-fields-examples.png" alt=""/></a></p>
-      <p>This is the option that enables the syntactic analysis (under the heading <strong>Java Compiler &gt; Errors/Warnings</strong>):</p>
-	  <p><img src="images/option-syntactic-null-analysis-for-fields.png" alt=""/></p>
-	</td>
-  </tr>   
-  <tr id="Support-for-package-Javadoc-in-Javadoc-hover-and-view">
-    <td class="title">Support for package Javadoc in Javadoc hover and view</td>
-    <td class="content">
-      The Javadoc hover and view now display package Javadoc from either the package-info.java or the package.html file.
-      <p><img src="images/package-javadoc-hover-examples.png" alt=""/></p>
-    </td>
-  </tr>
-  <tr id="Quick-Assist-for-unused-type-parameters">
-    <td class="title">Quick Assist for unused type parameters</td>
-    <td class="content">
-      The Java editor now provides a Quick Assist (<b>Ctrl+1</b>) to remove or document unused type parameters.
-      <p><img src="images/quickassist-for-unused-type-parameter-example.png" alt=""/></p>
-    </td>
-  </tr>
-  <tr id="pre-fill-package-name">
-	<td class="title">Pre-filling package name in creation wizards</td>
-	<td class="content">
-      All the type and package creation wizards now pre-fill the package name
-      if a suitable package name can be suggested for the selected project or source folder.
-      <p><img src="images/pre-fill-package-name.png" alt=""/></p>
-      <p>The suggested package name is the name of the project if the source folder does not contain any package
-      and if the project name is a valid package name.
-      In case of type creation wizards, if the source folder contains exactly one package then the name of that package
-      is used as the suggested package name.</p>
-  </td>
-  </tr>
-  
-  
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  
-  <tr id="bundles-in-category-editor">
-    <td class="title">Bundles in the category editor</td>
-    <td class="content">
-      The category editor now supports putting individual bundles into categories.
-      <p>      
-      The category editor creates a category.xml that can define categories that the contents of
-      a p2 repository should be organized into.  Previously only features could be specified as belonging
-      to a category and be visible to users.  Now individual bundles can be added to the category.xml.
-      </p>
-      <p>
-      <img src="images/category-editor.png" alt="Category editor can include individual bundles"/>
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="plugin-classpath-contributors">
-    <td class="title">New API to contribute to the classpath of plug-in projects</td>
-    <td class="content">
-      New API in PDE allows you to add additional classpath entries to a plug-in project.  Contribute a 
-      <em>Plug-in Classpath Contributor</em> via the <em>org.eclipse.pde.core.pluginClasspathContributors</em>
-      extension point.  Whenever the PDE classpath is computed or a new plug-in dependency is added, your classpath
-      contributor will be queried for additional entries.
-      <p>
-      If you are using Equinox Adapter hooks to load additional libraries at runtime you can use this API to add 
-      the correct libraries to the classpath at build time.
-      </p>
-      <p>
-      <img src="images/classpath-contributor.png" alt="An example classpath contributor extension"/>
-      </p>
-      </td>
-  </tr>
-  
-  <tr id="update-classpath-workspace">
-    <td class="title">Updating the classpath requires a workspace lock</td>
-    <td class="content">
-      When a change is made to a plug-in that forces a classpath update, an update job is created that
-      modifies the Plug-in Dependencies classpath container in the background. This job now acquires a workspace lock
-      to prevent other operations such as builders from running on a stale classpath.
-      <p>
-      This behaviour can be enabled in 4.2.2 by setting the system property <em>pde.lockWorkspaceForClasspath</em> to 
-      true.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="api-use-filters">
-    <td class="title">Problem filters apply to API Tools use scans</td>
-    <td class="content">
-      Problem filter files (.api_filter) can be used to filter problems reported by the API Tools analysis
-      task and the workspace analysis builder.  These filter files can now be applied to API Tools use scans.
-      Reference problems that are filtered out of the analysis results can be also filtered from the results
-      of use scans.
-      <p>
-      Filters are specified in the task using the same property as the analysis task.  Set the <em>filters</em>
-      attribute on the <em>apitooling.apiuse</em> task, specifying the root directory of API filter files.  Each
-      filter file must be in a folder with a filename matching the component name the filter file applies to.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="missing-filters-on-tasks">
-    <td class="title">API Tools tasks warn about missing include or exclude files</td>
-    <td class="content">
-      Many of the API Tools tasks, including Analysis, API Use, and API Freeze, provide <em>includelist</em> and
-      <em>excludelist</em> attributes which can be used to limit the reported problems. Previously,
-      if you set an include or exclude list, but the file wasn't found, the task would continue without warning
-      about the incorrect filtering.  Now a missing include or exclude list will result in the task failing with
-      an explanation.
-      <p>
-      <img src="images/missing-include.png" alt="Example console output for missing include"/>
-      </p>
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-
-  <tr id="detect-shared-install-change">
-    <td class="title">Detection of shared install changes</td>
-    <td class="content">
-	  When Eclipse is running in a read-only folder (also known as shared install) and the read-only
-	  installation has changed (e.g. new plugins installed, new version of Eclipse installed), Eclipse 
-	  will now detect this change and warn that your personal additional plugins have been uninstalled.
-	  In the next milestone, this warning will be replaced by a migration dialog allowing you to 
-	  reinstall your plugins.
-	  <p>
-      <img src="images/install-modified.png" alt="Dialog warning about a modified install"/>
-      </p>
-    </td>
-  </tr>
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Kepler milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M4-201212140730/news/">New for Eclipse Kepler milestone build M4 (December 14, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M3-201210312000/news/">New for Eclipse Kepler milestone build M3 (November 2, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M2-201209201300/news/">New for Eclipse Kepler milestone build M2 (September 21, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M1-201208101300/news/">New for Eclipse Kepler milestone build M1 (August 10, 2012)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.3/M5/images/category-editor.png b/platform/4.3/M5/images/category-editor.png
deleted file mode 100644
index 9c49163..0000000
--- a/platform/4.3/M5/images/category-editor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M5/images/classpath-contributor.png b/platform/4.3/M5/images/classpath-contributor.png
deleted file mode 100644
index 67e2913..0000000
--- a/platform/4.3/M5/images/classpath-contributor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M5/images/install-modified.png b/platform/4.3/M5/images/install-modified.png
deleted file mode 100644
index 29e5043..0000000
--- a/platform/4.3/M5/images/install-modified.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M5/images/missing-include.png b/platform/4.3/M5/images/missing-include.png
deleted file mode 100644
index 304a810..0000000
--- a/platform/4.3/M5/images/missing-include.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M5/images/null-annotations-for-fields-examples.png b/platform/4.3/M5/images/null-annotations-for-fields-examples.png
deleted file mode 100644
index 4276694..0000000
--- a/platform/4.3/M5/images/null-annotations-for-fields-examples.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M5/images/null-annotations-for-fields-examples.txt b/platform/4.3/M5/images/null-annotations-for-fields-examples.txt
deleted file mode 100644
index 648bc94..0000000
--- a/platform/4.3/M5/images/null-annotations-for-fields-examples.txt
+++ /dev/null
@@ -1,26 +0,0 @@
-import org.eclipse.jdt.annotation.NonNull;
-import org.eclipse.jdt.annotation.Nullable;
-
-public class NullAnnotatedFields {
-    @NonNull Letter nonNull;
-    @Nullable Letter nullable;
-    String test() {
-        nonNull.print();
-        nullable.print();
-        nonNull = null;
-
-        if (nullable != null)
-            nullable.print(); // protected
-
-        nullable = new Letter();
-        bar();     // spoils protection
-        return nullable.toString();
-    }
-    void bar() {
-       
-    }
-}
-// --- not shown in the screenshot: --- 
-class Letter {
-    void print() {}
-}
\ No newline at end of file
diff --git a/platform/4.3/M5/images/option-syntactic-null-analysis-for-fields.png b/platform/4.3/M5/images/option-syntactic-null-analysis-for-fields.png
deleted file mode 100644
index fbe2422..0000000
--- a/platform/4.3/M5/images/option-syntactic-null-analysis-for-fields.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M5/images/package-javadoc-hover-examples.png b/platform/4.3/M5/images/package-javadoc-hover-examples.png
deleted file mode 100644
index 8a580c9..0000000
--- a/platform/4.3/M5/images/package-javadoc-hover-examples.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M5/images/pre-fill-package-name.png b/platform/4.3/M5/images/pre-fill-package-name.png
deleted file mode 100644
index 230704e..0000000
--- a/platform/4.3/M5/images/pre-fill-package-name.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M5/images/quickassist-for-unused-type-parameter-example.png b/platform/4.3/M5/images/quickassist-for-unused-type-parameter-example.png
deleted file mode 100644
index 5c63e66..0000000
--- a/platform/4.3/M5/images/quickassist-for-unused-type-parameter-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M6/default_style.css b/platform/4.3/M6/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.3/M6/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.3/M6/eclipse-news-M6.html b/platform/4.3/M6/eclipse-news-M6.html
deleted file mode 100644
index ab73d1d..0000000
--- a/platform/4.3/M6/eclipse-news-M6.html
+++ /dev/null
@@ -1,169 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Project 4.3 M6 News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.3 M6 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M6 
-  (March 15, 2013) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-</ul>
-
-<!-- IMPORTANT: Follow instructions in ../whats-new-template/eclipse-whats-new-template.html -->
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  <tr id="migrationWizard">
-    <td class="title">Migration Wizard</td>
-    <td class="content">
-     Building on the changes introduced in M5 to detect changes in shared installs, Eclipse now includes a migration wizard to help users through the re-ininstallation of their plug-ins.
-	 <p>This wizard is presented in two situations. First, when a read-only installation of Eclipse is being changed (i.e. Eclipse is being updated or plugins are added / remove), second when a new read-only installation of Eclipse is run for the first time.</p>
-     <p><img src="images/migration-wizard.png" alt=""/></p>
-    </td>
-  </tr>
-  <tr id="linkColor">
-    <td class="title">BIDI Text Direction</td>
-    <td class="content">
-     New API has been added to allow text direction to be set independent of the widget orientation. For more info see <a href="http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/examples/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet364.java">Snippet 364</a>.
-     <p><img src="images/bidi.png" alt=""/></p>
-    </td>
-  </tr>
-  <tr id="bidi">
-    <td class="title">New SWT color constant for hyperlinks</td>
-    <td class="content">
-     A new constant (SWT_COLOR_LINK_FOREGROUND) has been added that will return the native color of hyperlinks on all platforms.
-     <p><img src="images/linkColor.png" alt=""/></p>
-    </td>
-  </tr>
-  <tr id="whole-word-option">
-    <td class="title">Whole word option on File Search page</td>
-    <td class="content">
-     The <b>File Search</b> page now allows to search for words via a new option:
-     <p><img src="images/whole-word-option.png" alt=""/></p>
-    </td>
-  </tr>
-  <tr id="use-last-page-option">
-    <td class="title">Open Search dialog on last used page</td>
-    <td class="content">
-     The Search dialog can now be configured to open on the last used page, instead of computing the best matching page based on the current selection:
-     <p><img src="images/use-last-page-option.png" alt=""/></p>
-    </td>
-  </tr>
- 
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr id="convert-to-if-return">
-    <td class="title">'Convert to if-!-return' Quick Assist</td>
-    <td class="content">
-     Ever encountered a long <code>if</code> statement that can be safely inverted to an early return, so that you can ignore the code that follows, and make it easier to understand? 
-     Now, you can just use a Quick Assist <b>(Ctrl+1)</b> on the <code>if</code> statement to do this refactoring:
-     <p><img src="images/convert-to-if-!-return.png" alt=""/></p>
-    </td>
-  </tr>
-
-  <tr id="linked-Javadoc-package-names">
-   <td class="title">Package names are linked in Javadoc hover and view</td>
-   <td class="content">
-     You can now click individual package names displayed in the header of the Javadoc hover or the Javadoc view to see the package Javadoc:
-     <p><img src="images/javadoc-package-names-linked.png" alt=""/></p>
-   </td>
-  </tr>
-   <tr id="InfoViews-should-indicate-when-linking-is-outOfSync">
-   <td class="title">Javadoc and Declaration view indicate when out of sync</td>
-   <td class="content">
-     The Javadoc and Declaration view now indicate when their content is no longer in sync with the current selection:
-     <p><img src="images/declaration-view-indicating-outofsync.png" alt=""/></p>
-   </td>
-  </tr>
-  
-  <tr id="junit-4-11">
-    <td class="title">Only one JUnit (4.11)</td>
-    <td class="content">
-        The org.junit bundle has been updated to
-        <a href="http://htmlpreview.github.com/?https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.html">JUnit 4.11</a>.
-      <p>
-        At the same time, our good old friend org.junit_3.8.2 has been retired, and the org.junit4 compatibility bundle
-        has also been removed. Your <code>Require-Bundle:</code> entries should just point to
-        <code>org.junit;bundle-version="4.11.0"</code> (or an earlier version, if you like).
-      </p>
-      <p>Note that JUnit 4 still contains the JUnit 3 APIs. If you need org.junit_3.8.2 back for
-        whatever reason, you can still get it from <a href="http://download.eclipse.org/tools/orbit/downloads/">Orbit</a>.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="debug-improved-generics-eval">
-   <td class="title">Improved evaluation of generics while debugging</td>
-   <td class="content">
-     Significant improvements have been made in the debug evaluation engine to support the use of
-     generics. This impacts the use of conditional breakpoints, the display view, the expressions view,
-     and the inspect/display/execute actions. Previously, evaluations acting on classes with generics
-     would sometimes encounter compilation errors.
-   </td>
-  </tr>
-  
-  <tr id="debug-ext-source-api">
-   <td class="title">API to contribute location information for non-standard JRE / JDK libraries</td>
-   <td class="content">
-     JDT Debug now provides an extension point <code>org.eclipse.jdt.launching.libraryLocationResolvers</code>
-     that you can use to contribute location information for non-standard JRE / JDK libraries.  For example,
-     this extension point can be used to provide Javadoc and source locations for JARs in the ext location
-     of a JRE.
-     <p>
-     Extenders must provide an implementation of <code>org.eclipse.jdt.launching.ILibraryLocationResolver</code>
-     which can provide package roots, source paths, Javadoc locations and index locations for a library.
-     </p> 
-   </td>
-  </tr>
-  
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  <tr id="api-unresolved-bundles">
-   <td class="title">API Tools Analysis and Freeze tasks can run with unresolved bundles</td>
-   <td class="content">
-	 The API Tools <b>Analysis</b> and <b>API Freeze</b> Ant tasks will now process bundles
-	 with resolver errors such as missing dependencies.  This means you can now get analysis results
-	 for an incomplete product.
-	 <p>
-     The Ant tasks produce reports based on a reference baseline and a profile.  Previously both 
-     the baseline and the profile had to describe complete products.  Any bundle that had resolver 
-     errors due to missing dependencies would be skipped.  Now these bundles will be processed.
-     </p>
-     <p>
-     Resolver errors can affect the results, therefore a list of resolver errors is included in the XML output
-     and warnings are added to the HTML report. To return to the old behavior of skipping
-     unresolved bundles, you can set <code>processunresolvedbundles="false"</code> on your Ant task.
-     </p>
-     <p>
-     <img src="images/unresolved-analysis.png" alt="Unresolved bundle in the analysis task"/>
-     </p>
-   </td>
-  </tr>
-
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Kepler milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M5a-201302041400/news/">New for Eclipse Kepler milestone build M5a (February 5, 2013)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M4-201212140730/news/">New for Eclipse Kepler milestone build M4 (December 14, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M3-201210312000/news/">New for Eclipse Kepler milestone build M3 (November 2, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M2-201209201300/news/">New for Eclipse Kepler milestone build M2 (September 21, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M1-201208101300/news/">New for Eclipse Kepler milestone build M1 (August 10, 2012)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.3/M6/images/bidi.png b/platform/4.3/M6/images/bidi.png
deleted file mode 100644
index 4aa20af..0000000
--- a/platform/4.3/M6/images/bidi.png
+++ /dev/null
Binary files differ
diff --git "a/platform/4.3/M6/images/convert-to-if-\041-return.png" "b/platform/4.3/M6/images/convert-to-if-\041-return.png"
deleted file mode 100644
index 5cd0b93..0000000
--- "a/platform/4.3/M6/images/convert-to-if-\041-return.png"
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M6/images/declaration-view-indicating-outofsync.png b/platform/4.3/M6/images/declaration-view-indicating-outofsync.png
deleted file mode 100644
index 4e5e98d..0000000
--- a/platform/4.3/M6/images/declaration-view-indicating-outofsync.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M6/images/javadoc-package-names-linked.png b/platform/4.3/M6/images/javadoc-package-names-linked.png
deleted file mode 100644
index b7254fe..0000000
--- a/platform/4.3/M6/images/javadoc-package-names-linked.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M6/images/linkColor.png b/platform/4.3/M6/images/linkColor.png
deleted file mode 100644
index c6f4381..0000000
--- a/platform/4.3/M6/images/linkColor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M6/images/migration-wizard.png b/platform/4.3/M6/images/migration-wizard.png
deleted file mode 100644
index 095b024..0000000
--- a/platform/4.3/M6/images/migration-wizard.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M6/images/unresolved-analysis.png b/platform/4.3/M6/images/unresolved-analysis.png
deleted file mode 100644
index b92b1a6..0000000
--- a/platform/4.3/M6/images/unresolved-analysis.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M6/images/use-last-page-option.png b/platform/4.3/M6/images/use-last-page-option.png
deleted file mode 100644
index 806f02e..0000000
--- a/platform/4.3/M6/images/use-last-page-option.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M6/images/whole-word-option.png b/platform/4.3/M6/images/whole-word-option.png
deleted file mode 100644
index ec15556..0000000
--- a/platform/4.3/M6/images/whole-word-option.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/default_style.css b/platform/4.3/M7/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.3/M7/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.3/M7/eclipse-news-M7.html b/platform/4.3/M7/eclipse-news-M7.html
deleted file mode 100644
index b8e2221..0000000
--- a/platform/4.3/M7/eclipse-news-M7.html
+++ /dev/null
@@ -1,271 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Project 4.3 M7 News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.3 M7 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M7 
-(May 3, 2013) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  <tr id="e4-api">
-    <td class="title">Initial Eclipse 4 API released</td>
-    <td class="content">
-      As was announced at EclipseCon this year, the first set of official API based on the new Eclipse 
-      Platform 4 architecture is now available. This is the first step in allowing developers to use the 
-      new simpler and more powerful mechanisms to build Eclipse plug-ins and applications.
-    <p>
-      This API is comprised of two basic concepts:
-    </p><p>
-      <b>The user interface model</b>: The content of this model describes the structure of the user interface.
-      The Eclipse Platform reacts to changes in this model by updating the presentation, and the complete
-      model is now available through the new API.
-    </p><p>
-      Note that the model represents everything on the screen and these elements can be modified
-      by your code (see the example below).
-    </p><p>
-      <b>IEclipseContext / Dependency Injection (DI)</b>: Contexts are containers of UI runtime state
-      including all the available services. The typical Eclipse Platform 4 pattern is that contributions
-      are created and configured through dependency injection based on state and services found in the local
-      context for that model element.
-    </p><p>
-      Here are a few links to more information about the UI Model, the services and DI (the Javadoc and supporting
-      Eclipse documentation will be available before Kepler is released):
-    </p>
-    <ul>
-      <li><a href="http://www.eclipsecon.org/2013/sites/eclipsecon.org.2013/files/FormalAPI.pdf">EclipseCon 2013 API Slides</a></li>
-      <li><a href="http://www.vogella.com/articles/EclipseRCP/article.html">Lars' RCP Tutorial</a></li>
-      <li><a href="http://www.vogella.com/articles/Eclipse4Services/article.html">Lars' Services Tutorial</a></li>
-      <li><a href="http://eclipsesource.com/blogs/2013/04/18/eclipse-4-e4-tutorial-behavior-annotations/">Jonas Helming's DI Tutorials</a></li>
-    </ul>
-    <p>
-      There is quite a lot of information already available for Eclipse Platform 4. While parts of the API are just being
-      formalized now, most of the concepts and API existed in provisional form in previous Eclipse 4 releases.
-    </p><p>
-      Just to give a taste of what working in a modeled UI is all about, here's a code snippet showing
-      how to get a 'standard' Command handler to toggle the visibility of the 'Quick Access' text field
-      that appears in the top trim. First we gain access to the model by getting the MApplication as a
-      'service'. Form there we can access the EModelService and use it to find the model element
-      representing the search in the UI. Then it's just a simple matter of toggling the element's
-      'toBeRendered' flag to get it to (dis)appear.
-    </p>
-    <pre>
-public Object execute(ExecutionEvent event) throws ExecutionException {
-  IWorkbenchWindow window = HandlerUtil.getActiveWorkbenchWindowChecked(event);		
-  MApplication theApp = (MApplication) window.getService(MApplication.class);
-  MWindow activeWin = theApp.getSelectedElement();
-  EModelService ms = activeWin.getContext().get(EModelService.class);
-  EPartService ps = activeWin.getContext().get(EPartService.class);
-  MToolControl search = (MToolControl) ms.find("SearchField", activeWin);
-  if (search != null) {
-    search.setToBeRendered(!search.isToBeRendered());
-    window.getShell().layout(true, true);
-  }
-  return null;
-}
-      </pre>
-    </td>
-  </tr>
-
-  <tr id="xulrunner64">
-    <td class="title">XULRunner on 64-bit Windows</td>
-    <td class="content">The browser widget now supports the embedding of XULRunner on Windows x86_64.</td>
-  </tr> 
-
-  <tr id="open-resource-buttons">
-    <td class="title">Open Resource dialog enhancements</td>
-    <td class="content">
-      The <b>Open Resource</b> (<b>Ctrl+Shift+R</b>) dialog now offers direct access to the
-      <b>Show In</b> and <b>Open With</b> menus via drop-down buttons. On platforms that
-      support mnemonics, the buttons are also accessible via <b>Alt+W</b> and <b>Alt+H</b>.
-      <p><img src="images/open-resource-buttons.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="remediation"> 
-    <td class="title">Installation Remediation</td>
-    <td class="content">
-	 In order to help you deal with dependency errors while installing software, the various installation wizards now contain 
-	 a new wizard page. This page, called <b>remediation</b>, proposes various solutions in order to help you proceed 
-	 with the installation, even when the exact change you requested is not possible.
-	 <p>
-	 The picture below shows a screenshot of this page in action. In this particular case the user is trying to install something
-	 that is conflicting with what is installed, and the wizard gives the option to update what is installed so that the installation
-	 can proceed.
-	 </p>
-     <p><img src="images/remediation.png" alt=""/></p>
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  
-  <tr id="remove-type-arguments">
-    <td class="title">Remove type arguments after content assist</td>
-    <td class="content">
-     Ever encountered a case where content assist added type arguments for a generic type, but you do not want them
-     because you need the <code>.class</code> literal or you want to invoke a static method?
-     Now, rather than deleting all the arguments manually, 
-     you can just delete the '<code>&lt;</code>' and that will remove the entire text up to '<code>&gt;</code>'.
-    </td>
-  </tr>
-  <tr id="proposals-without-prefix">
-    <td class="title">Template and keyword proposals without prefix</td>
-    <td class="content">
-      Content assist now proposes templates and keywords without needing a prefix first:
-      <p><img src="images/content-assist.png" alt=""/></p>
-    </td>
-  </tr>
-  <tr id="semicolon-key-inserts-method">
-    <td class="title">Use ';' key to insert method invocation</td>
-    <td class="content">
-    Irrespective of the return type of a method, you can now use the semicolon (<b>;</b>) key to select any method invocation proposal
-    from the content assist popup. The '<code>;</code>' will be appended at the end of the method invocation.
-    </td>
-  </tr>   
-  <tr id="semicolon-appended-for-void-methods">
-    <td class="title">Content assist appends ';' to void methods</td>
-    <td class="content">
-    If a void method is selected during content assist, then a semicolon is now automatically
-    appended at the end of the method invocation.
-    </td>
-  </tr>
-  <tr id="test-templates">
-    <td class="title">JUnit test templates</td>
-    <td class="content">
-      The JUnit test templates have been renamed to show the JUnit 4 template before the JUnit 3 template:
-      <p><img src="images/junit-templates.png" alt="'test' for JUnit 4; 'test3' for JUnit 3"/></p>
-    </td>
-  </tr>
-  <tr id="junit-view-assumptions">
-    <td class="title">JUnit view shows assumption failures</td>
-    <td class="content">
-      The JUnit view now counts <code>@Ignore</code>d tests and tests that didn't meet
-      an assumption as "skipped' tests. The skipped tests also got new icons, and
-      tests with an assumption failure no longer get the 'passed' checkmark.
-      <p><img src="images/junit-view-assumptions.png" alt="Test cases using @Ignore and Assume.assumeFalse(true)"/></p>
-    </td>
-  </tr>
-  <tr id="create-loop-variable">
-    <td class="title">Quick Fix to create 'for' loop variable</td>
-    <td class="content">
-      The new <b>Create loop variable</b> quick fix corrects an incomplete 'for' loop
-      by adding the type of the loop variable.
-      <p><img src="images/create-loop-variable.png" alt="Corrects 'for (e: elements) {}' to 'for (ElementType e: elements) {}'"/></p>
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  <tr id="auto-start-all-plugins">
-    <td class="title">Default start level settings apply to all plug-ins</td>
-    <td class="content">
-      When editing the <b>Plug-ins</b> tab of an <b>Eclipse Application</b> launch configuration, the <b>Default
-      Start level</b> and <b>Default Auto-start</b> settings chosen at the top of the tab will be used when launching with
-      all workspace and enabled target plug-ins.  Previously this setting would only be used when launching a
-      specific list of plug-ins.
-      <p><img src="images/autostart-all-plugins.png" alt="All plug-ins selected on the tab"/></p>
-      <p><img src="images/autostart-levels.png" alt="Different default start level settings"/></p>
-    </td>
-  </tr>
-  <tr id="pde-run-remembers-selection">
-    <td class="title">Running from PDE editors remembers previous launch</td>
-    <td class="content">
-      The PDE editors allow applications to be launched from the top toolbar of the <b>Manifest</b>, <b>Plug-in</b>
-      and <b>Product</b> editors.  By default PDE only provides one type of application to launch.  However, if you have additional tooling
-      installed such as RAP Tools, different application launches will be available in a drop down menu.
-      <p><img src="images/launch-order.png" alt="Ordering of launches in editor"/></p>
-      <p>
-      This menu now remembers which application was launched most recently and puts it at the top of the list.  The most
-      recent choice will be launched if the run button is pressed.  The order is saved between workbench
-      restarts.
-      </p>
-    </td>
-  </tr>
-  <tr id="pde-junit-e4">
-    <td class="title">JUnit plug-in tests can run on Eclipse platform 4 workbench</td>
-    <td class="content">
-      Applications that use the Eclipse Platform 4 workbench API can now
-      use <b>JUnit Plug-in Test</b> launch configurations to test their plug-ins. Previously 
-      the tests would require the 3.x workbench API from the <code>org.eclipse.ui</code> bundle to 
-      hook into the workbench lifecycle.
-    </td>
-  </tr>
-  <tr id="support-pre-osgi-bundles">
-    <td class="title">API Tools has limited support for pre-OSGi Eclipse plug-ins</td>
-    <td class="content">
-      Eclipse plug-ins created before 3.1 did not contain an OSGi bundle manifest.  API Tools
-      can now convert the pre-OSGi plug-ins to valid components in an API baseline.  This allows
-      analysis, use and freeze scans to process plug-ins that depend on pre-OSGi plug-ins instead
-      of failing to resolve.
-      <p><img src="images/use-scan.png" alt="Use scan launch configuration with pre-OSGi plug-ins"/></p>
-      <p>
-      An OSGi runtime is required to do the conversion.  Tasks run using Eclipse AntRunner
-      or the API Use Report external tools launch configuration can convert the plug-ins.  Tasks
-      run from the command line Ant runner will skip pre-OSGi plug-ins.
-      </p>
-    </td>
-  </tr>
-    <tr id="noreference-types">
-    <td class="title">API Tools allows @noreference Javadoc tag on types</td>
-    <td class="content">
-      API Tools now allows the use of the <code>@noreference</code> Javadoc tag on types (classes, interfaces,
-      annotations and enums).
-      <p><img src="images/no-reference.png" alt="Type defining noreference Javadoc tag"/></p>
-      <p>Placing this tag restricts the API so that any reference to that type or its members
-      will be flagged as invalid API use.</p>
-      <p><img src="images/using-no-reference.png" alt="Class trying to reference a type marked as noreference"/></p>
-      <p>
-      To mark a type in an API package as not being API, tag it as <code>@noreference</code>,
-      <code>@noextend</code> and <code>@noinstantiate</code> (or <code>@noimplement</code>).  This ensures that
-      no client can access it via valid API and the type could later be removed.
-      </p>
-    </td>
-  </tr>
-    <tr id="api-tags-check-visibility">
-    <td class="title">API Tools Javadoc tags check visibility</td>
-    <td class="content">
-      A member that is not publicly visible, such as a method or field marked private, is not part 
-      of API.  Any API Tools Javadoc tags on it are invalid.  Now, API Tools will also check if a
-      member is not visible because of the visibility of an enclosing type.  If the member is not visible,
-      any tags on it will be considered invalid.
-      <p><img src="images/api-parent-not-visible.png" alt="Javadoc tag flagged as invalid because member is not visible"/></p>
-      <p>
-      Tag validation is turned off by default.  To turn it on for your API Tools enabled project, open 
-      <b>Project Properties > Plug-in Development > API Errors/Warnings</b>.  Set 
-      <b>API Use > General > Unsupported use of API Javadoc tags</b> to <code>Warning</code> or <code>Error</code>.
-      </p>
-    </td>
-  </tr>
-
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Kepler milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M6-201303141330/news/">New for Eclipse Kepler milestone build M6 (March 15, 2013)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M5a-201302041400/news/">New for Eclipse Kepler milestone build M5a (February 5, 2013)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M4-201212140730/news/">New for Eclipse Kepler milestone build M4 (December 14, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M3-201210312000/news/">New for Eclipse Kepler milestone build M3 (November 2, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M2-201209201300/news/">New for Eclipse Kepler milestone build M2 (September 21, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M1-201208101300/news/">New for Eclipse Kepler milestone build M1 (August 10, 2012)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.3/M7/images/api-parent-not-visible.png b/platform/4.3/M7/images/api-parent-not-visible.png
deleted file mode 100644
index 1003977..0000000
--- a/platform/4.3/M7/images/api-parent-not-visible.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/autostart-all-plugins.png b/platform/4.3/M7/images/autostart-all-plugins.png
deleted file mode 100644
index 3858413..0000000
--- a/platform/4.3/M7/images/autostart-all-plugins.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/autostart-levels.png b/platform/4.3/M7/images/autostart-levels.png
deleted file mode 100644
index 4f00f01..0000000
--- a/platform/4.3/M7/images/autostart-levels.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/content-assist.png b/platform/4.3/M7/images/content-assist.png
deleted file mode 100644
index a3b003c..0000000
--- a/platform/4.3/M7/images/content-assist.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/create-loop-variable.png b/platform/4.3/M7/images/create-loop-variable.png
deleted file mode 100644
index c23d4de..0000000
--- a/platform/4.3/M7/images/create-loop-variable.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/junit-templates.png b/platform/4.3/M7/images/junit-templates.png
deleted file mode 100644
index 00a9a62..0000000
--- a/platform/4.3/M7/images/junit-templates.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/junit-view-assumptions.png b/platform/4.3/M7/images/junit-view-assumptions.png
deleted file mode 100644
index 4f29f91..0000000
--- a/platform/4.3/M7/images/junit-view-assumptions.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/launch-order.png b/platform/4.3/M7/images/launch-order.png
deleted file mode 100644
index d85ca91..0000000
--- a/platform/4.3/M7/images/launch-order.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/no-reference.png b/platform/4.3/M7/images/no-reference.png
deleted file mode 100644
index 45d52bc..0000000
--- a/platform/4.3/M7/images/no-reference.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/open-resource-buttons.png b/platform/4.3/M7/images/open-resource-buttons.png
deleted file mode 100644
index a741513..0000000
--- a/platform/4.3/M7/images/open-resource-buttons.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/remediation.png b/platform/4.3/M7/images/remediation.png
deleted file mode 100644
index 63c576b..0000000
--- a/platform/4.3/M7/images/remediation.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/use-scan.png b/platform/4.3/M7/images/use-scan.png
deleted file mode 100644
index f91028e..0000000
--- a/platform/4.3/M7/images/use-scan.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/M7/images/using-no-reference.png b/platform/4.3/M7/images/using-no-reference.png
deleted file mode 100644
index 51518c8..0000000
--- a/platform/4.3/M7/images/using-no-reference.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/MX/default_style.css b/platform/4.3/MX/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.3/MX/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.3/MX/eclipse-news-MX.html b/platform/4.3/MX/eclipse-news-MX.html
deleted file mode 100644
index ee6a54c..0000000
--- a/platform/4.3/MX/eclipse-news-MX.html
+++ /dev/null
@@ -1,136 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Project 4.3 MX News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.3 MX - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build MX 
-  (Month dd, yyyy) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-  <li><a href="#Equinox">Equinox</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Resources</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">SWT</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Platform UI</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">User Assistance</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Platform Text</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Team/CVS</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Compare</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Ant</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr> 
-    <td colspan="2">  <div class="title">Debug</div>
-      </td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="Equinox">Equinox</td>
-  </tr>
-  <tr> 
-    <td colspan="2"><div align="left">[ <em>Not available yet</em> ]</div></td>
-  </tr>
-
-  <tr> 
-    <td colspan="2">  <div class="title">Template</div>
-      </td>
-  </tr>
-  <tr id="first-item">
-    <td class="title">First item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Kepler milestone builds:</p>
-<ul>
-  <li>New for Eclipse Kepler milestone build M7 (May 3, 2013)</li>
-  <li>New for Eclipse Kepler milestone build M6 (March 15, 2013)</li>
-  <li>New for Eclipse Kepler milestone build M5 (February 1, 2013)</li>
-  <li>New for Eclipse Kepler milestone build M4 (December 14, 2012)</li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M3-201210312000/news/">New for Eclipse Kepler milestone build M3 (November 2, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M2-201209201300/news/">New for Eclipse Kepler milestone build M2 (September 21, 2012)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.3M1-201208101300/news/">New for Eclipse Kepler milestone build M1 (August 10, 2012)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.3/final - SR2/default_style.css b/platform/4.3/final - SR2/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.3/final - SR2/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.3/final - SR2/eclipse-news-part1.html b/platform/4.3/final - SR2/eclipse-news-part1.html
deleted file mode 100644
index 31ac5a1..0000000
--- a/platform/4.3/final - SR2/eclipse-news-part1.html
+++ /dev/null
@@ -1,187 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2013, 2014. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Project Kepler - New and Noteworthy</title>
-</head>
-<body>
-<h2>Platform and Equinox</h2>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table class="news" cellpadding="10" cellspacing="0">
-
-  <tr id="detached-sash">
-    <td class="title">Detached windows with sash</td>
-    <td class="content">
-      When you detach a view or editor into its own separate window, it now
-      has all the capabilities of a normal workbench window. They now support multiple stacks of
-      views separated by sashes with arbitrary layouts. The detached parts will remain synchronized
-      with the master window that they were detached from. This is especially handy for people developing
-      with two or more monitors, so they can spread views across several monitors and keep them synchronized.
-		<p><img src="images/detached-sash.png" alt="Detached window with multiple views separated by sash."/></p>
-    </td>
-  </tr>
-
-   <tr id="detect-shared-install-change">
-    <td class="title">Detection of shared install changes</td>
-    <td class="content">
-	  When running in a read-only folder (also known as shared install) and the read-only
-	  installation has changed (e.g. new plugins installed, new version of Eclipse installed), Eclipse 
-	  will now detect this change and warn that your personal additional plugins have been uninstalled.
-	  A migration wizard will then guide you through the steps to re-install your plug-ins, if they are
-	  still compatible with your other installed software.
-	 <p>This wizard is presented in two situations. First, when a read-only installation is being 
-	 changed (i.e. your application is being updated or plugins are added or removed), second when a new read-only 
-	 installation is run for the first time.</p>
-     <p><img src="images/migration-wizard.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="remediation"> 
-    <td class="title">Installation Remediation</td>
-    <td class="content">
-	 In order to help you deal with dependency errors while installing software, the various installation wizards now contain 
-	 a new wizard page. This page, called <b>remediation</b>, proposes various solutions in order to help you proceed 
-	 with the installation, even when the exact change you requested is not possible.
-	 <p>
-	 The picture below shows a screenshot of this page in action. In this particular case the user is trying to install something
-	 that is conflicting with what is installed, and the wizard gives the option to update what is installed so that the installation
-	 can proceed.
-	 </p>
-     <p><img src="images/remediation.png" alt=""/></p>
-    </td>
-  </tr>
-
-  <tr id="gtk3">
-    <td class="title">SWT for GTK3</td>
-    <td class="content">
-      32-bit and 64-bit GTK3 have joined the lineup of supported configurations for which SWT and Eclipse are routinely built. This implementation is currently early access. Everyone is encouraged to download and test these new builds, and to log bugs in <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform">bugzilla</a>.
-      <p>To load the SWT GTK3 libraries, you must set the environment variable <code>SWT_GTK3</code> to <code>1</code> prior to starting Eclipse. (ex. export <code>SWT_GTK3=1</code>)</p>
-      <p><img src="images/gtk3.png" alt="GTK3 Control Example"/></p>
-      <p><strong>Importamt Note:</strong> The Linux GTK+ 3 port of SWT is broken for GTK+ versions above 3.8.x.
-      This primarily affects users running Fedora 20, Ubuntu 14.04 (Alpha builds), openSUSE 13.1 and any other Linux distributions that bundle GTK+ 3.10.x
-      (see bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127">421127</a>).</p>
-        
-	</td>
-  </tr>
-
-   <tr id="performance">
-    <td class="title">Performance enhancements</td>
-    <td class="content">
-      Significant performance enhancements have been made in the Platform user interface in this release. In particular, some applications
-      that were experiencing slow editor opening, closing, and switching are now much faster. Editor selection changes and the <b>Open Resource</b>
-      dialog have also been made faster. A number of leaks have been addressed to ensure
-      long-running applications don't run out of memory.
-      <p><img src="images/speed.jpg" alt="Speedometer"/><br/>
-	  <small>Photographer: YtseJam Photography / Creative Commons Attribution 2.0</small>
-	  </p>
-	</td>
-  </tr>
-
-  <tr id="trim-drag">
-    <td class="title">Trim dragging</td>
-    <td class="content">
-      You can now drag toolbars to reposition them. 
-      <p><img src="images/trim-drag.png" alt="Dragging a toolbar."/></p>
-      <p>The perspective switcher can also be dragged to the left or right of the window and it will switch to a 
-        vertical orientation.</p>
-	  <p><img src="images/vertical-switcher.png" alt="Dragging perspective switcher to vertical orientation."/></p>
-    </td>
-  </tr>
-
-  <tr id="import-nested">
-    <td class="title">Import nested projects</td>
-    <td class="content">
-      The <b>Import Projects</b> wizard now has an option to continue searching for projects to import
-      recursively within any project it finds. This allows you to import physically nested projects
-      at the same time.
-      <p><img src="images/import-nested.png" alt="Import nested projects."/></p>
-    </td>
-  </tr>
-
-  <tr id="open-resource-buttons">
-    <td class="title">Open Resource dialog enhancements</td>
-    <td class="content">
-      The <b>Open Resource</b> (<b>Ctrl+Shift+R</b>) dialog now offers direct access to the
-      <b>Show In</b> and <b>Open With</b> menus via drop-down buttons. On platforms that
-      support mnemonics, the buttons are also accessible via <b>Alt+W</b> and <b>Alt+H</b>.
-      <p><img src="images/open-resource-buttons.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="whole-word-option">
-    <td class="title">Whole word option on File Search page</td>
-    <td class="content">
-     The <b>File Search</b> page now allows to search for words via a new option:
-     <p><img src="images/whole-word-option.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="use-last-page-option">
-    <td class="title">Open Search dialog on last used page</td>
-    <td class="content">
-     The Search dialog can now be configured to open on the last used page, instead of 
-     computing the best matching page based on the current selection:
-     <p><img src="images/use-last-page-option.png" alt=""/></p>
-    </td>
-  </tr>
-
-  <tr id="launch-dialog-warnings">
-    <td class="title">Launch configuration dialog can show warnings</td>
-    <td class="content">
-      Previously, contributors could only set an 'ok' or an 'error' state in their launch configuration tags / groups. Now,
-      contributors can set a warning state with a message for their tabs / groups - possibly warning users about set options
-      that might be problematic, but do not necessarily need to prevent launching.
-      <p><img src="images/lcd-warnings.png" alt="Launch configuration dialog showing warning message / state"/></p>
-    </td>
-  </tr>
-  
-  <tr id="x-start-on-first-thread">
-    <td class="title">Option to omit <span style="letter-spacing:-0.05em;">-XstartOnFirstThread</span></td>
-    <td class="content">
-      If you are launching an SWT program on Mac OS X, you can now selectively add / remove the <code>-XstartOnFirstThread</code> VM argument
-      in the event your VM does not support it. This option can be configured per launch configuration and is available on the standard Arguments
-      tab for Java configurations (Java Application, Eclipse, etc.).
-      <p><img src="images/x-start-on-first-thread.png" alt="New VM preference allowing users to selectively add the -XstartOnFirstThread argument per-configuration"/></p>
-    </td>
-  </tr>
-
-  <tr id="ant-augment">
-    <td class="title">Support for the Ant augment task</td>
-    <td class="content">
-      The Ant editor now has support for the Ant
-      <a href="http://ant.apache.org/manual/Tasks/augment.html">
-      <code>augment</code></a> task.  
-    </td>
-  </tr>
-  
-  <tr id="stop-thread">
-    <td class="title">Stop thread from OSGi console</td>
-    <td class="content">
-      If a bad plug-in runs into an endless loop, then you previously had to kill the whole Eclipse process.
-      Now, you can launch Eclipse with <code>-console [[host:]port]</code> to get a safety ring.
-      If you're then stuck in an endless loop and Eclipse doesn't respond any more, you can just execute
-      <pre>osgi&gt; threads stop main</pre>
-      at the OSGi prompt. This will send an IllegalStateException to the "main" thread.
-      This is usually enough to stop the endless loop, but keep the Eclipse workbench running.
-      <p>If you don't want to keep a console window around, you can pass a port number (e.g. 12345) after
-      the <code>-console</code> command line argument and later use <code>telnet localhost:12345</code> to connect.</p>
-    </td>
-  </tr>
-
-  <!-- ****************** END OF N&N TABLE ****************** -->
-</table>
-
-<p align="center"><font color="#808080">Previous</font>&nbsp;&nbsp;&nbsp;&nbsp; <a href="eclipse-news-part2.html">Next</a></p>
-</body>
-</html>
diff --git a/platform/4.3/final - SR2/eclipse-news-part2.html b/platform/4.3/final - SR2/eclipse-news-part2.html
deleted file mode 100644
index 91d4729..0000000
--- a/platform/4.3/final - SR2/eclipse-news-part2.html
+++ /dev/null
@@ -1,478 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2013. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Project Kepler - New and Noteworthy</title>
-</head>
-<body>
-<h2>Java development tools</h2>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-
-<table class="news" cellpadding="10" cellspacing="0">
-
-  <!-- ******************* Java Editor ************************************* -->
-  <tr>
-    <td id="JavaEditor" class="section" colspan="2">
-    <h2>Java Editor </h2>
-    </td>
-  </tr>
-  
-  <tr id="convert-if-else-to-switch">
-    <td class="title">New 'Convert if-else to switch' Quick Assist</td>
-    <td class="content">
-      The new <b>Convert 'if-else' to 'switch'</b> quick assist (<b>Ctrl+1</b>) allows you to convert an if-else statement to 
-      an equivalent switch statement:
-      <p><img src="images/convert-if-else-to-switch.png" alt=""/></p>
-      
-      This quick assist is the reverse of the existing <b>Convert 'switch' to 'if-else'</b> quick assist.
-    </td>
-  </tr>  
-    
-  <tr id="convert-to-if-return">
-    <td class="title">'Convert to if-!-return' Quick Assist</td>
-    <td class="content">
-     Ever encountered a long <code>if</code> statement that can be safely inverted to an early return, so that you can ignore the code that follows, and make it easier to understand? 
-     Now, you can just use a quick assist <b>(Ctrl+1)</b> on the <code>if</code> statement to do this refactoring:
-     <p><img src="images/convert-to-if-!-return.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="create-loop-variable">
-    <td class="title">Quick Fix to create 'for' loop variable</td>
-    <td class="content">
-      The new <b>Create loop variable</b> quick fix corrects an incomplete 'for' loop
-      by adding the type of the loop variable:
-      <p><img src="images/create-loop-variable.png" alt="Corrects 'for (e: elements) {}' to 'for (ElementType e: elements) {}'"/></p>
-    </td>
-  </tr>
-          
-  <tr id="combine-strings">
-    <td class="title">Quick Assist to combine Strings</td>
-    <td class="content">
-      The new <b>Combine to single String</b> quick assist (<b>Ctrl+1</b>) replaces String concatenations
-      with a single String literal:
-      <p>
-        <img src="images/combine-strings.png" alt="String s = &quot;Delete &quot; + &quot;two&quot; + &quot; files?&quot; // becomes: String s = &quot;Delete two files?&quot;"/>
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="Quick-Assist-for-unused-type-parameters">
-    <td class="title">Quick Assist for unused type parameters</td>
-    <td class="content">
-      The Java editor now provides a quick assist (<b>Ctrl+1</b>) to remove or document unused type parameters:
-      <p><img src="images/quickassist-for-unused-type-parameter-example.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="proposals-without-prefix">
-    <td class="title">Template and keyword proposals without prefix</td>
-    <td class="content">
-      Content assist now proposes templates and keywords without needing a prefix first:
-      <p><img src="images/content-assist.png" alt=""/></p>
-    </td>
-  </tr>
-       
-  <tr id="remove-type-arguments">
-    <td class="title">Remove type arguments after content assist</td>
-    <td class="content">
-     Ever encountered a case where content assist added type arguments for a generic type, but you do not want them
-     because you need the <code>.class</code> literal or you want to invoke a static method?
-     Now, rather than deleting all the arguments manually, 
-     you can just delete the '<code>&lt;</code>' and that will remove the entire text up to '<code>&gt;</code>'.
-    </td>
-  </tr>
-  
-  <tr id="semicolon-appended-for-void-methods">
-    <td class="title">Content assist appends ';' to void methods</td>
-    <td class="content">
-    If a void method is selected during content assist, then a semicolon is now automatically
-    appended at the end of the method invocation.
-    </td>
-  </tr>
-  
-  <tr id="semicolon-key-inserts-method">
-    <td class="title">Use ';' key to insert method invocation</td>
-    <td class="content">
-    Irrespective of the return type of a method, you can now use the semicolon (<b>;</b>) key to select any method invocation proposal
-    from the content assist popup. The '<code>;</code>' will be appended at the end of the method invocation.
-    </td>
-  </tr>  
-  
-  <!-- ******************* Java Compiler ************************************* -->
-  <tr>
-    <td id="JavaCompiler" class="section" colspan="2">
-    <h2>Java Compiler</h2>
-    </td>
-  </tr>
-  
-  <tr id="content-assist-TL_CONSTRUCTOR_START">
-    <td class="title">New API to indicate content assist requested on the start of a constructor</td>
-    <td class="content">
-      org.eclipse.jdt.core.CompletionContext.TL_CONSTRUCTOR_START:
-      <pre>
-	  /**
-	   * The completed token is the first token of a constructor
-	   * invocation expression.
-	   * e.g.
-	   * 
-	   * public class X {
-	   *   public void bar() {
-	   *     new Foo| // completion occurs at |
-	   *   }
-	   * }
-	   */
-	</pre>
-    </td>
-  </tr>
-  
-   <tr id="tolerateIllegalAmbiguousVarargsInvocation">
-    <td class="title">Force Eclipse to compile (illegal) ambiguous varargs code</td>
-    <td class="content"> JDK 6 and below had a bug and considered the code below legal.
-	However, this bug was fixed in JDK 7 and the code now reports an ambiguous invocation error at the call site for test(..).
-	Eclipse Juno followed and fixed this across all compliance levels:
-	<p><a href="images/illegal-ambiguous-varargs-error.txt"><img src="images/illegal-ambiguous-varargs-error.png" alt="follow link for source"/></a></p>
-	<p>If you still want the above code to compile in compliance &lt; 1.7, to mimic JDK 6 or below, you can use the
-	system property <b>tolerateIllegalAmbiguousVarargsInvocation</b> to force Eclipse to tolerate such ambiguous varargs cases.
-	This property can e.g. be set in the eclipse.ini file after the -vmargs setting:</p>
-	<pre><code>...
-        	 -vmargs
-			-DtolerateIllegalAmbiguousVarargsInvocation=true
-			...</code></pre>
-	<p><i>Note</i>: With this setting, Eclipse also	mimics JDK 6 and below in raising an error in other cases that are legal in both JDK 7 and Eclipse:</p>
-	<p><a href="images/illegal-ambiguous-varargs-error2.txt"><img src="images/illegal-ambiguous-varargs-error2.png" alt="follow link for source"/></a></p>
-	</td>
-  </tr>
-
-  <tr id="new-batch-compiler-options">
-    <td class="title">New batch compiler options</td>
-    <td class="content"> If you use the ECJ batch compiler using the command line or Ant tasks, you can now configure the following options which previously could only be set through
-	the <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings</b> page:
-	<ul>
-      <li>invalidJavadoc: set all warnings for malformed Javadoc tags</li>
-      <li>invalidJavadocTag: validate Javadoc tag arguments</li>
-      <li>invalidJavadocTagDep: validate deprecated references in Javadoc tag args</li>
-      <li>invalidJavadocTagNotVisible: validate non-visible references in Javadoc tag args</li>
-      <li>invalidJavadocVisibility(&lt;visibility&gt;): specify visibility modifier for malformed Javadoc tag warnings</li>
-      <li>missingJavadocTags: enable detection of missing Javadoc tags</li>
-      <li>missingJavadocTagsOverriding: detect missing Javadoc tags in overriding methods</li>
-      <li>missingJavadocTagsMethod: detect missing Javadoc tags for method type parameter</li>
-      <li>missingJavadocTagsVisibility(&lt;visibility&gt;): specify visibility modifier for missing Javadoc tags warnings</li>
-      <li>missingJavadocComments: detect missing Javadoc comments</li>
-      <li>missingJavadocCommentsOverriding: detect missing Javadoc tags in overriding methods</li>
-      <li>missingJavadocCommentsVisibility(&lt;visibility&gt;): specify visibility modifier for missing Javadoc comments warnings</li>
-      <li>nullAnnotConflict: detect conflict between null annotation specified and nullness inferred. Is effective only with nullAnnot option enabled</li>
-      <li>nullAnnotRedundant: detect redundant specification of null annotation. Is effective only with nullAnnot option enabled</li>
-      <li>nullUncheckedConversion: detect unchecked conversion from non-annotated type to @NonNull type. Is effective only with nullAnnot option enabled</li>
-      <li>unusedParam: detect unused parameter</li>
-      <li>unusedParamOverriding: detect unused parameter for overriding method</li>
-      <li>unusedParamImplementing: detect unused parameter for implementing method</li>
-      <li>unusedParamIncludeDoc: detect unused parameter documented in comment tag</li>
-      <li>unusedThrownWhenOverriding: detect unused declared thrown exception in overriding method</li>
-      <li>unusedThrownIncludeDocComment: detect unused declared thrown exception, documented in a comment tag</li>
-      <li>unusedThrownExemptExceptionThrowable: detect unused declared thrown exception, exempt Exception and Throwable</li>
-	</ul>
-	<p> For more information on using batch compiler options, please refer to <b>Help &gt; Java Development User Guide &gt; Tasks &gt; Compiling Java Code &gt; Using the batch compiler</b>.</p>
-    </td>
-  </tr>
-      
-  <tr id="unused-type-parameter">
-    <td class="title">Option to omit @Override for interface methods</td>
-    <td class="content">
-      Eclipse can add <code>@Override</code> annotations for overriding methods:
-      <p>
-        <img src="images/override-annotation-code-style.png" alt="Code Style preference page"/>
-      </p>
-      <p>
-        If your code uses Java 1.6 or higher, the <code>@Override</code> annotation is also added to
-        methods that override an interface method. If you don't want to use <code>@Override</code>
-        in this case, then follow the link and disable the corresponding compiler option:
-      </p>
-      <p>
-        <img src="images/override-annotation-compiler.png" alt="Errors/Warnings preference page, checkbox 'Include implementations of interface methods (1.6 or higher)'"/>
-      </p>
-      <p>
-        You may also want to enable the diagnostic for Missing '@Override' annotation.   
-      </p>
-    </td>
-  </tr>
-    
-  <tr id="detection-unused-type-parameter">
-    <td class="title">Detection of unused type parameters</td>
-    <td class="content">
-      The compiler can now detect unused type parameters:
-      <p>
-        <img src="images/unused-type-parameter.png" alt=""/>
-      </p>
-      <p>
-        The <b>Unused type parameter</b> diagnostic is set to Ignore by default and can be enabled on the 
-		<b>Java &gt; Compiler &gt; Errors/Warnings</b>
-		preference page.
-      </p>
-    </td>
-  </tr>  
-  
-  <tr id="inherit-null-annotations">
-    <td class="title">Option to inherit null annotations</td>
-    <td class="content">
-        JDT has a new option controlling how to interpret null annotations in the presence of inheritance.
-        This should facilitate the migration towards null annotations in projects with
-        mixed code ownership.
-      <p>For the sake of code readability, JDT expects null annotations of an overridden
-        method to be repeated in overriding methods. In the following example the analysis
-        normally complains that <code>arg</code> is not annotated in <code>ClientClass</code>,
-        which means, this class doesn't formally conform to the contract of its super-interface:
-      </p>
-      <p><img title="Example for inheritance of null annotations" src="images/inherit-null-annotations-example.png" 
-          alt="Example for inheritance of null annotations"/></p>
-      <p>Starting with 4.3M4 this behavior can be changed by selecting the option
-        <strong>Inherit null annotations</strong>:
-      </p>
-      <p><img title="Option for inheritance of null annotations" src="images/inherit-null-annotations-option.png"
-           alt="Option for inheritance of null annotations"/></p>
-      <p>In this new mode the analysis implicitly fills in all missing annotations
-        in overriding methods and uses the annotations from the overridden method.
-        In the above example the error will go away, and analysis concludes that the
-        code is actually safe, which is likely when the contract had already been
-        defined in the javadoc comment and the implementor actually adheres to that
-        contract. If, on the other hand, the implementation does not comply with the
-        inherited specification, new errors will be reported as shown below:
-      </p>
-      <p><img title="Negative example for inheritance of null annotations" src="images/inherit-null-annotations-example2.png"
-          alt="Negative example for inheritance of null annotations"/></p>
-      <p>If inheritance of null annotations encounters any ambiguity or conflict
-        the analysis falls back to requiring explicit annotations.
-      </p>
-    </td>
-  </tr>
-
-  <tr id="null-annotations-for-fields">
-    <td class="title">Null annotations for fields</td>
-    <td class="content">
-      The annotation-based null analysis &mdash; first released with Eclipse Indigo &mdash; has been extended
-      to apply also to fields. If enabled, this analysis will now detect the following problems
-      concerning any field annotated with <code>@NonNull</code>:
-      <ul>
-      <li>If the field is not properly initialized to a non-null value.</li>
-      <li>If a value is assigned to the field that is not known to be non-null.</li>
-      </ul>
-      <p>In return to these obligations, dereferencing a <code>@NonNull</code> field is regarded as always safe.
-      </p>
-      <p>If a field is marked as <code>@Nullable</code>, generally every direct dereference
-        of the field is flagged as a potential null pointer access. Even a null check for such a field is not
-        a perfect protection due to dangers of side effects, effects via aliased references, and concurrency.</p>
-      <p>As a compromise between safety and convenience, the compiler can be configured to apply
-        <strong>"syntactic null analysis for fields"</strong>.
-        With this option enabled, the compiler syntactically recognizes
-        a narrow range of code patterns where a null-check of a field is <em>directly</em> followed by
-        a dereference or an assignment to a <code>@NonNull</code> variable. For these particular situations,
-        no problem will be reported.</p>
-      <p>In the following example, the check in line 12 properly protects the access in line 13, whereas
-        the knowledge that field <code>nullable</code> holds a non-null value (in line 15) is spoiled by
-        the intermediate statement in line 16:</p>
-	  <p><a href="images/null-annotations-for-fields-examples.txt"><img src="images/null-annotations-for-fields-examples.png" alt=""/></a></p>
-      <p>This is the option that enables the syntactic analysis (under the heading <strong>Java Compiler &gt; Errors/Warnings</strong>):</p>
-	  <p><img src="images/option-syntactic-null-analysis-for-fields.png" alt=""/></p>
-	</td>
-  </tr>   
- 
-  <tr id="close-quietly">
-    <td class="title">Leak analysis respects well-known utilities</td>
-    <td class="content">
-        JDT's analysis for resource leaks has been made aware of well known utilities
-        from google and apache libraries.
-      <p>Generally, this analysis looks for <code>close()</code> method calls
-        directly on a resource (any value of type <code>Closeable</code>).
-        However, in order to reduce boilerplate exception handling, several libraries
-        are providing methods like <code>closeQuietly(Closeable)</code>.
-        Previously, the analysis would complain about the missing call to <code>close()</code>
-        as shown below:
-      </p>
-      <p><img title="Example for close quietly" src="images/close-quietly-example.png"
-          alt="Example for close quietly"/></p>
-      <p>This warning is not relevant and will no longer be reported.
-        To achieve this, JDT now hardcodes a (short) white list of functions that
-        are known to safely close a given resource.
-      </p>
-    </td>
-  </tr>
-  
-  <!-- ******************* Java Views and Dialogs ************************************* -->
-  <tr>
-    <td id="JavaViews" class="section" colspan="2">
-    <h2>Java Views and Dialogs</h2>
-    </td>
-  </tr>
-  
-  <tr id="pre-fill-package-name">
-	<td class="title">Pre-filling package name in creation wizards</td>
-	<td class="content">
-      All the type and package creation wizards now pre-fill the package name
-      if a suitable package name can be suggested for the selected project or source folder:
-      <p><img src="images/pre-fill-package-name.png" alt=""/></p>
-      <p>The suggested package name is the name of the project if the source folder does not contain any package
-      and if the project name is a valid package name.
-      In case of type creation wizards, if the source folder contains exactly one package then the name of that package
-      is used as the suggested package name.</p>
-   </td>
-  </tr>
-  
-   <tr id="content-assist-additional-info-in-debug-views">
-    <td class="title">Content assist shows Javadoc in Display, Expressions and Variables view</td>
-    <td class="content">
-        Content assist in the Display, Expressions and Variables view now shows Javadoc:
-		<p><img src="images/additional-info.png" alt="Screenshot showing Javadoc when doing content assist"/></p>
-	</td>
-  </tr>
-  
-  <tr id="javadoc-view-target">
-    <td class="title">Javadoc view resolves enclosing method call and keeps last target</td>
-    <td class="content">
-      The <b>Javadoc</b> and <b>Declaration</b> views now try to find the enclosing method call
-      if the selection or caret position doesn't resolve to a valid Java element:
-      <p>
-        <img src="images/javadoc-view-target.png" alt="'String.copyValueOf(data, offset, count)', with 'data' selected."/>
-      </p>
-      Furthermore, they keep the last resolved target element even if no new target can be resolved.
-    </td>
-  </tr>
-  
-  <tr id="Support-for-package-Javadoc-in-Javadoc-hover-and-view">
-    <td class="title">Support for package Javadoc in Javadoc hover and view</td>
-    <td class="content">
-      The Javadoc hover and view now display package Javadoc from either the
-      <code style="white-space:nowrap;">package-info.java</code> or the <code>package.html</code> file:
-      <p><img src="images/package-javadoc-hover-examples.png" alt=""/></p>
-    </td>
-  </tr>
-    
-  <tr id="linked-Javadoc-package-names">
-   <td class="title">Package names are linked in Javadoc hover and view</td>
-   <td class="content">
-     You can now click individual package names displayed in the header of the Javadoc hover or the Javadoc view to see the package Javadoc:
-     <p><img src="images/javadoc-package-names-linked.png" alt=""/></p>
-   </td>
-  </tr>  
-  
-   <tr id="InfoViews-should-indicate-when-linking-is-outOfSync">
-   <td class="title">Javadoc and Declaration view indicate when out of sync</td>
-   <td class="content">
-     The Javadoc and Declaration view now indicate when their content is no longer in sync with the current selection:
-     <p><img src="images/declaration-view-indicating-outofsync.png" alt=""/></p>
-   </td>
-  </tr>
-  
-  <!-- *********************** Debug ******************************** -->
-  <tr>
-    <td id="Debug" class="section" colspan="2">
-    <h2>Debug</h2>
-    </td>
-  </tr>  
-     
-  <tr id="debug-improved-generics-eval">
-   <td class="title">Improved evaluation of generics while debugging</td>
-   <td class="content">
-     Significant improvements have been made in the debug evaluation engine to support the use of
-     generics. This impacts the use of conditional breakpoints, the display view, the expressions view,
-     and the inspect/display/execute actions. Previously, evaluations acting on classes with generics
-     would sometimes encounter compilation errors.
-   </td>
-  </tr>
-   
-  <tr id="debug-ext-source-api">
-   <td class="title">API to contribute location information for non-standard JRE / JDK libraries</td>
-   <td class="content">
-     JDT Debug now provides an extension point <code>org.eclipse.jdt.launching.libraryLocationResolvers</code>
-     that you can use to contribute location information for non-standard JRE / JDK libraries.  For example,
-     this extension point can be used to provide Javadoc and source locations for JARs in the ext location
-     of a JRE.
-     <p>
-     Extenders must provide an implementation of <code>org.eclipse.jdt.launching.ILibraryLocationResolver</code>
-     which can provide package roots, source paths, Javadoc locations and index locations for a library.
-     </p> 
-   </td>
-  </tr>  
-  
-  <tr id="xml-dom-structure">
-    <td class="title">XML DOM logical structures</td>
-    <td class="content">
-      JDT now provides a default logical structure for XML DOMs, which can be used during debugging to view the children and attributes of a node as simple arrays:
-      <p>
-      <img src="images/dom-structure.png" alt="Variables view showing the XML DOM logical structure"/>
-      </p>
-    </td>
-  </tr>
-
-   <tr id="only-include-exported-entries">
-    <td class="title">Global preference to include exported entries during launching</td>
-    <td class="content">
-      A new global preference has been added so you can only allow exported classpath entries to be used during launching. Previously, this 
-      was only customizable per launch configuration on the default classpath entry on the Java Classpath tab. The new preference does not affect 
-      launch configuration data, so no migration is needed.
-      
-      <p>
-      The new preference can be found on the <b>Java &gt; Debug</b> preference page.</p>
-      <p><img src="images/only-include-exported.png" alt="New global preference to only include exported classpath entries"/></p>
-      
-    </td>
-  </tr>
-
-  <!-- ******************* JUnit ************************************* -->
-  <tr>
-    <td id="JUnit" class="section" colspan="2">
-    <h2>JUnit</h2>
-    </td>
-  </tr>
-    
-  <tr id="junit-4-11">
-    <td class="title">Only one JUnit (4.11)</td>
-    <td class="content">
-        The org.junit bundle has been updated to
-        <a href="http://htmlpreview.github.com/?https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.html">JUnit 4.11</a>.
-      <p>
-        At the same time, our good old friend org.junit_3.8.2 has been retired, and the org.junit4 compatibility bundle
-        has also been removed. Your <code>Require-Bundle:</code> entries should just point to
-        <code>org.junit;bundle-version="4.11.0"</code> (or an earlier version, if you like).
-      </p>
-      <p>Note that JUnit 4 still contains the JUnit 3 APIs. If you need org.junit_3.8.2 back for
-        whatever reason, you can still get it from <a href="http://download.eclipse.org/tools/orbit/downloads/">Orbit</a>.
-      </p>
-    </td>
-  </tr>
-
-  <tr id="test-templates">
-    <td class="title">JUnit test templates</td>
-    <td class="content">
-      The JUnit test templates have been renamed to show the JUnit 4 template before the JUnit 3 template:
-      <p><img src="images/junit-templates.png" alt="'test' for JUnit 4; 'test3' for JUnit 3"/></p>
-    </td>
-  </tr>
-  
-  <tr id="junit-view-assumptions">
-    <td class="title">JUnit view shows assumption failures</td>
-    <td class="content">
-      The JUnit view now counts <code>@Ignore</code>d tests and tests that didn't meet
-      an assumption as "skipped' tests. The skipped tests also got new icons, and
-      tests with an assumption failure no longer get the 'passed' checkmark:
-      <p><img src="images/junit-view-assumptions.png" alt="Test cases using @Ignore and Assume.assumeFalse(true)"/></p>
-    </td>
-  </tr>
- 
-    <!-- ****************** END OF N&N TABLE ****************** -->
-</table>
-
-<p align="center"><a href="eclipse-news-part1.html">Previous</a>&nbsp;&nbsp;&nbsp;&nbsp; <a href="eclipse-news-part3.html">Next</a></p>
-</body>
-
-</html>
diff --git a/platform/4.3/final - SR2/eclipse-news-part3.html b/platform/4.3/final - SR2/eclipse-news-part3.html
deleted file mode 100644
index 05c71c4..0000000
--- a/platform/4.3/final - SR2/eclipse-news-part3.html
+++ /dev/null
@@ -1,143 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2013. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Project Kepler - New and Noteworthy</title>
-</head>
-<body>
-
-<h2>Platform and Equinox API</h2>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table class="news" cellpadding="10" cellspacing="0">
-<tbody>
-  <!-- ******************** Platform ********************** -->
-  <tr>
-    <td id="Platform" class="section" colspan="2"><h2>Platform Changes</h2></td>
-  </tr>
-  
-  <tr id="e4-api">
-    <td class="title">Initial Eclipse 4 API released</td>
-    <td class="content">
-      The first set of official API based on the new Eclipse Platform 4 architecture is now available. 
-      This is the first step in allowing developers to use the new simpler and more powerful mechanisms 
-      to build Eclipse plug-ins and applications.
-    <p>
-      This API is comprised of two basic concepts:
-    </p><p>
-      <b>The user interface model</b>: The content of this model describes the structure of the user interface.
-      The Eclipse Platform reacts to changes in this model by updating the presentation, and the complete
-      model is now available through the new API.
-    </p><p>
-      Note that the model represents everything on the screen and these elements can be modified
-      by your code (see the example below).
-    </p><p>
-      <b>IEclipseContext / Dependency Injection (DI)</b>: Contexts are containers of UI runtime state
-      including all the available services. The typical Eclipse Platform 4 pattern is that contributions
-      are created and configured through dependency injection based on state and services found in the local
-      context for that model element.
-    </p><p>
-      Here are a few links to more information about the UI Model, the services and DI (the Javadoc and supporting
-      Eclipse documentation will be available before Kepler is released):
-    </p>
-    <ul>
-      <li><a href="http://www.eclipsecon.org/2013/sites/eclipsecon.org.2013/files/FormalAPI.pdf">EclipseCon 2013 API Slides</a></li>
-      <li><a href="http://www.vogella.com/articles/EclipseRCP/article.html">Lars' RCP Tutorial</a></li>
-      <li><a href="http://www.vogella.com/articles/Eclipse4Services/article.html">Lars' Services Tutorial</a></li>
-      <li><a href="http://eclipsesource.com/blogs/2013/04/18/eclipse-4-e4-tutorial-behavior-annotations/">Jonas Helming's DI Tutorials</a></li>
-    </ul>
-    <p>
-      There is quite a lot of information already available for Eclipse Platform 4. While parts of the API are just being
-      formalized now, most of the concepts and API existed in provisional form in previous Eclipse 4 releases.
-    </p><p>
-      Just to give a taste of what working in a modeled UI is all about, here's a code snippet showing
-      how to get a 'standard' Command handler to toggle the visibility of the 'Quick Access' text field
-      that appears in the top trim. First we gain access to the model by getting the MApplication as a
-      'service'. Form there we can access the EModelService and use it to find the model element
-      representing the search in the UI. Then it's just a simple matter of toggling the element's
-      'toBeRendered' flag to get it to (dis)appear.
-    </p>
-    <pre>
-public Object execute(ExecutionEvent e) throws ExecutionException {
-  IWorkbenchWindow window = HandlerUtil.getActiveWorkbenchWindowChecked(e);
-  MApplication theApp = (MApplication) window.getService(MApplication.class);
-  MWindow activeWin = theApp.getSelectedElement();
-  EModelService ms = activeWin.getContext().get(EModelService.class);
-  EPartService ps = activeWin.getContext().get(EPartService.class);
-  MToolControl search = (MToolControl) ms.find("SearchField", activeWin);
-  if (search != null) {
-    search.setToBeRendered(!search.isToBeRendered());
-    window.getShell().layout(true, true);
-  }
-  return null;
-}
-      </pre>
-    </td>
-  </tr>
-
-  <tr id="ua-lucene">
-    <td class="title">Migrated to Lucene 3.5</td>
-    <td class="content">
-      The Eclipse platform help system has migrated from Lucene 2.9.1 to Lucene 3.5.
-      This change brings improved performance and many bug fixes in help search.
-      Some old help system API related to Lucene has been changed or removed as part
-      of this fix. Refer to the platform 4.3 migration guide for more details.
-    </td>
-  </tr>  
-  
-  <tr id="ant184">
-    <td class="title">Platform updated to Ant 1.8.4</td>
-    <td class="content">
-      The platform has been updated to use Apache Ant version 1.8.4. To see what is new in version 1.8.4 you can
-      check the <a href="http://apache.mirrors.tds.net/ant/README.html">Apache Ant what's new</a>.
-    </td>
-  </tr> 
-
-
-  <!-- *********************** SWT *********************** -->
-  <tr>
-    <td id="SWT" class="section" colspan="2"><h2>SWT Changes</h2></td>
-  </tr>
-
-  <tr id="xulrunner64">
-    <td class="title">XULRunner on 64-bit Windows</td>
-    <td class="content">The browser widget now supports the embedding of XULRunner on Windows x86_64.</td>
-  </tr> 
-
-  <tr id="bidi">
-    <td class="title">New SWT color constant for hyperlinks</td>
-    <td class="content">
-     A new constant (SWT_COLOR_LINK_FOREGROUND) has been added that returns the native color of hyperlinks on all platforms.
-     <p><img src="images/linkColor.png" alt=""/></p>
-    </td>
-  </tr>
-    
-  <tr id="linkColor">
-    <td class="title">BIDI Text Direction</td>
-    <td class="content">
-     New API has been added to allow text direction to be set independent of the widget orientation.
-     Note that this API is currently only implemented on Windows. 
-     <p>For more info see <a href="http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/examples/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet364.java">Snippet 364</a>.
-     </p>
-     <p><img src="images/bidi.png" alt=""/></p>
-    </td>
-  </tr>
-
-  </tbody>
-<!-- ****************** END OF N&N TABLE ****************** -->
-</table>
-
-<p align="center"><a href="eclipse-news-part2.html">Previous</a>&nbsp;&nbsp;&nbsp;&nbsp; <a href="eclipse-news-part4.html">Next</a></p>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/platform/4.3/final - SR2/eclipse-news-part4.html b/platform/4.3/final - SR2/eclipse-news-part4.html
deleted file mode 100644
index 2bd4523..0000000
--- a/platform/4.3/final - SR2/eclipse-news-part4.html
+++ /dev/null
@@ -1,327 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2013. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Project Kepler - New and Noteworthy</title>
-</head>
-<body>
-<div style="font-size: 20px; font-weight: bold;">Plug-in Development Environment</div>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table class="news" cellpadding="10" cellspacing="0">
-  <tbody>
-  
-  <!-- ******************** APITools ********************** -->
-  <tr>
-    <td id="APITools" class="section" colspan="2"><h2>API Tools</h2></td>
-  </tr>
-
-  <tr id="ee-desc-feature">
-    <td class="title">New API Tools EE descriptions feature</td>
-    <td class="content">
-      The API Tools Execution Environment descriptions are now supplied on the Eclipse update sites as a single
-      installable feature.  The feature includes the descriptions for all supported execution environments.
-      
-       <p><img src="images/eedescfeature.png" alt="New EE Desc feature on update sites"/></p> 
-    </td>
-  </tr>
-  
-    <tr id="noreference-types">
-    <td class="title">API Tools allows @noreference Javadoc tag on types</td>
-    <td class="content">
-      API Tools now allows the use of the <code>@noreference</code> Javadoc tag on types (classes, interfaces,
-      annotations and enums).
-      <p><img src="images/no-reference.png" alt="Type defining noreference Javadoc tag"/></p>
-      <p>Placing this tag restricts the API so that any reference to that type or its members
-      will be flagged as invalid API use.</p>
-      <p><img src="images/using-no-reference.png" alt="Class trying to reference a type marked as noreference"/></p>
-      <p>
-      To mark a type in an API package as not being API, tag it as <code>@noreference</code>,
-      <code>@noextend</code> and <code>@noinstantiate</code> (or <code>@noimplement</code>).  This ensures that
-      no client can access it via valid API and the type could later be removed.
-      </p>
-    </td>
-  </tr>
-  
-    <tr id="api-tags-check-visibility">
-    <td class="title">API Tools Javadoc tags check visibility</td>
-    <td class="content">
-      A member that is not publicly visible, such as a method or field marked private, is not part 
-      of API.  Any API Tools Javadoc tags on it are invalid.  Now, API Tools will also check if a
-      member is not visible because of the visibility of an enclosing type.  If the member is not visible,
-      any tags on it will be considered invalid.
-      <p><img src="images/api-parent-not-visible.png" alt="Javadoc tag flagged as invalid because member is not visible"/></p>
-      <p>
-      Tag validation is turned off by default.  To turn it on for your API Tools enabled project, open 
-      <b>Project Properties > Plug-in Development > API Errors/Warnings</b>.  Set 
-      <b>API Use > General > Unsupported use of API Javadoc tags</b> to <code>Warning</code> or <code>Error</code>.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="support-pre-osgi-bundles">
-    <td class="title">API Tools has limited support for pre-OSGi Eclipse plug-ins</td>
-    <td class="content">
-      Eclipse plug-ins created before 3.1 did not contain an OSGi bundle manifest.  API Tools
-      can now convert the pre-OSGi plug-ins to valid components in an API baseline.  This allows
-      analysis, use and freeze scans to process plug-ins that depend on pre-OSGi plug-ins instead
-      of failing to resolve.
-      <p><img src="images/use-scan.png" alt="Use scan launch configuration with pre-OSGi plug-ins"/></p>
-      <p>
-      An OSGi runtime is required to do the conversion.  Tasks run using Eclipse AntRunner
-      or the API Use Report external tools launch configuration can convert the plug-ins.  Tasks
-      run from the command line Ant runner will skip pre-OSGi plug-ins.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="api-unresolved-bundles">
-   <td class="title">API Tools Analysis and Freeze tasks can run with unresolved bundles</td>
-   <td class="content">
-	 The API Tools <b>Analysis</b> and <b>API Freeze</b> Ant tasks will now process bundles
-	 with resolver errors such as missing dependencies.  This means you can now get analysis results
-	 for an incomplete product.
-	 <p>
-     The Ant tasks produce reports based on a reference baseline and a profile.  Previously both 
-     the baseline and the profile had to describe complete products.  Any bundle that had resolver 
-     errors due to missing dependencies would be skipped.  Now these bundles will be processed.
-     </p>
-     <p>
-     Resolver errors can affect the results, therefore a list of resolver errors is included in the XML output
-     and warnings are added to the HTML report. To return to the old behavior of skipping
-     unresolved bundles, you can set <code>processunresolvedbundles="false"</code> on your Ant task.
-     </p>
-     <p>
-     <img src="images/unresolved-analysis.png" alt="Unresolved bundle in the analysis task"/>
-     </p>
-   </td>
-  </tr>
-  
-  <tr id="api-use-filters">
-    <td class="title">Problem filters apply to API Tools use scans</td>
-    <td class="content">
-      Problem filter files (.api_filter) can be used to filter problems reported by the API Tools analysis
-      task and the workspace analysis builder.  These filter files can now be applied to API Tools use scans.
-      Reference problems that are filtered out of the analysis results can also be filtered from the results
-      of use scans.
-      <p>
-      Filters are specified in the task using the same property as the analysis task.  Set the <em>filters</em>
-      attribute on the <em>apitooling.apiuse</em> task, specifying the root directory of API filter files.  Each
-      filter file must be in a folder with a filename matching the component name the filter file applies to.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="missing-filters-on-tasks">
-    <td class="title">API Tools tasks warn about missing include or exclude files</td>
-    <td class="content">
-      Many of the API Tools tasks, including Analysis, API Use, and API Freeze, provide <em>includelist</em> and
-      <em>excludelist</em> attributes which can be used to limit the reported problems. Previously,
-      if you set an include or exclude list, but the file wasn't found, the task would continue without warning
-      about the incorrect filtering.  Now a missing include or exclude list will result in the task failing with
-      an explanation.
-      <p>
-      <img src="images/missing-include.png" alt="Example console output for missing include"/>
-      </p>
-    </td>
-  </tr>
-  
-  <!-- ******************** Views and Editors ********************** -->
-  <tr>
-    <td id="ViewsAndEditors" class="section" colspan="2"><h2>Views and Editors</h2></td>
-  </tr>
-
-  <tr id="improved-feature-selection">
-    <td class="title">Improved feature selection dialog</td>
-    <td class="content">
-      The feature selection dialog used in wizards and editors has been enhanced with better wildcard support
-      and filtering options.
-      
-       <p><img src="images/featureselection.png" alt="Improved feature selection dialog"/></p> 
-    </td>
-  </tr>
-      
-  <tr id="additional-type-info">
-    <td class="title">Javadoc hover available in plug-in manifest editor</td>
-    <td class="content">
-      When editing the plugin.xml or manifest.mf files using the <b>Plug-in Manifest Editor</b>, 
-      opening content assist for type proposals will now display additional Javadoc information.
-      <p>
-        <img src="images/additional-type-info.png" alt="Additional info Javadoc hover for type proposals"/>
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="import-package">
-    <td class="title">New import package quick fixes</td>
-    <td class="content">
-      New quick fixes are available when you have an unresolved type in a Java file.  If the unresolved type
-      can be found in a package exported by a plug-in, a quick fix will be available to add an import
-      package entry to your plug-in manifest.  There is also a quick fix to add the exporting plug-in to
-      your manifest's require bundle header.
-      <p>
-      <img src="images/import-package.png" alt="Import package quick fix on an unresolved type"/>
-      </p>
-      <p>
-      If a package providing the type is available but the package is not exported by its plug-in, a quick fix will
-      offer to fix the providing plug-in's manifest. Only plug-ins in the workspace can be modified this
-      way.
-      </p>
-      <p>
-      <img src="images/export-package.png" alt="Export package quick fix on an unresolved type that is not exported"/>
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="bundles-in-category-editor">
-    <td class="title">Bundles in the category editor</td>
-    <td class="content">
-      The category editor now supports putting individual bundles into categories.
-      <p>      
-      The category editor creates a category.xml that can define categories that the contents of
-      a p2 repository should be organized into.  Previously only features could be specified as belonging
-      to a category and be visible to users.  Now individual bundles can be added to the category.xml.
-      </p>
-      <p>
-      <img src="images/category-editor.png" alt="Category editor can include individual bundles"/>
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="plugin-image-view">
-    <td class="title">Plug-in image browser view</td>
-    <td class="content">
-      A new view has been added to PDE.  The <b>Plug-in Image Browser</b> view displays icons and other
-      images from your target platform, running application or current workspace. 
-      <p>
-      	When an image is selected, additional information is displayed at the bottom of the view.  The
-        reference text can be used in plug-in extensions to refer to images in other bundles.
-      </p>
-      <p>
-        <img src="images/plugin-image-view.png" alt="The plug-in image browser view"/>
-      </p>
-    </td>
-  </tr>
-  
-  <!-- ******************** Misc ********************** -->
-  <tr>
-    <td id="Misc" class="section" colspan="2"><h2>Misc</h2></td>
-  </tr>
-
-  <tr id="default-launch-ee">
-    <td class="title">Launch configurations choose default execution environment</td>
-    <td class="content">
-      New PDE launch configurations (Eclipse Application, JUnit Plug-in Test, OSGi Framework) will
-      use a default execution environment to determine which Java runtime environment to launch with.
-      The launch configuration can be changed to use a different execution environment or a specific
-      JRE on the <b>Main</b> tab.
-      <p>
-        To find a valid execution environment, all known environments are checked against each bundle 
-        or plug-in that will be launched. Only an execution environment that is valid for all
-        plug-ins and bundles will be selected.  If no valid environment is found, a default JRE
-        will be chosen as before.
-      </p>
-      <p>
-        <img src="images/default-launch-ee.png" alt="Java runtime settings on the Main tab of PDE launch configurations"/>
-      </p>
-      <p>
-      	The JRE associated with the selected execution environment will be used to launch. To change 
-      	which JRE is associated with an execution environment, use the <b>Preferences > Java > Installed JREs > 
-      	Execution Environments</b> preference page.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="pde-5-bree">
-    <td class="title">PDE UI requires a 1.5 EE</td>
-    <td class="content">
-      The bundle required execution environment for the PDE UI bundles org.eclipse.pde.core and
-      org.eclipse.pde.ui is now J2SE-1.5.
-    </td>
-  </tr>
-  
-  <tr id="plugin-classpath-contributors">
-    <td class="title">New API to contribute to the classpath of plug-in projects</td>
-    <td class="content">
-      New API in PDE allows you to add additional classpath entries to a plug-in project.  Contribute a 
-      <em>Plug-in Classpath Contributor</em> via the <em>org.eclipse.pde.core.pluginClasspathContributors</em>
-      extension point.  Whenever the PDE classpath is computed or a new plug-in dependency is added, your classpath
-      contributor will be queried for additional entries.
-      <p>
-      If you are using Equinox Adapter hooks to load additional libraries at runtime you can use this API to add 
-      the correct libraries to the classpath at build time.
-      </p>
-      <p>
-      <img src="images/classpath-contributor.png" alt="An example classpath contributor extension"/>
-      </p>
-      </td>
-  </tr>
-  
-  <tr id="update-classpath-workspace">
-    <td class="title">Updating the classpath requires a workspace lock</td>
-    <td class="content">
-      When a change is made to a plug-in that forces a classpath update, an update job is created that
-      modifies the Plug-in Dependencies classpath container in the background. This job now acquires a workspace lock
-      to prevent other operations such as builders from running on a stale classpath.
-      <p>
-      This behaviour can be enabled in 4.2.2 by setting the system property <em>pde.lockWorkspaceForClasspath</em> to 
-      true.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="auto-start-all-plugins">
-    <td class="title">Default start level settings apply to all plug-ins</td>
-    <td class="content">
-      When editing the <b>Plug-ins</b> tab of an <b>Eclipse Application</b> launch configuration, the <b>Default
-      Start level</b> and <b>Default Auto-start</b> settings chosen at the top of the tab will be used when launching with
-      all workspace and enabled target plug-ins.  Previously this setting would only be used when launching a
-      specific list of plug-ins.
-      <p><img src="images/autostart-all-plugins.png" alt="All plug-ins selected on the tab"/></p>
-      <p><img src="images/autostart-levels.png" alt="Different default start level settings"/></p>
-    </td>
-  </tr>
-  
-  <tr id="pde-run-remembers-selection">
-    <td class="title">Running from PDE editors remembers previous launch</td>
-    <td class="content">
-      The PDE editors allow applications to be launched from the top toolbar of the <b>Manifest</b>, <b>Plug-in</b>
-      and <b>Product</b> editors.  By default PDE only provides one type of application to launch.  However, if you have additional tooling
-      installed such as RAP Tools, different application launches will be available in a drop down menu.
-      <p><img src="images/launch-order.png" alt="Ordering of launches in editor"/></p>
-      <p>
-      This menu now remembers which application was launched most recently and puts it at the top of the list.  The most
-      recent choice will be launched if the run button is pressed.  The order is saved between workbench
-      restarts.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="pde-junit-e4">
-    <td class="title">JUnit plug-in tests can run on Eclipse platform 4 workbench</td>
-    <td class="content">
-      Applications that use the Eclipse Platform 4 workbench API can now
-      use <b>JUnit Plug-in Test</b> launch configurations to test their plug-ins. Previously 
-      the tests would require the 3.x workbench API from the <code>org.eclipse.ui</code> bundle to 
-      hook into the workbench lifecycle.
-    </td>
-  </tr>
-  
-  <!-- ****************** END OF N&N TABLE ****************** -->
-  </tbody>
-</table>
-
-<p align="center"><a href="eclipse-news-part3.html">Previous</a>&nbsp;&nbsp;&nbsp;&nbsp; <font color="#808080">Next</font></p>
-
-</body>
-</html>
diff --git a/platform/4.3/final - SR2/eclipse-news.html b/platform/4.3/final - SR2/eclipse-news.html
deleted file mode 100644
index 94fd04e..0000000
--- a/platform/4.3/final - SR2/eclipse-news.html
+++ /dev/null
@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2012. This page is made available under license. For full details see: http://www.eclipse.org/legal/notice.html" >
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse Kepler - New and Noteworthy</title>
-</head>
-<body>
-
-<h1>Eclipse Kepler - New and Noteworthy</h1>
-
-<div align="right"><i>
-I demonstrate by means of philosophy that the earth is round, <br>
-and is inhabited on all sides; that it is insignificantly small, <br>
-and is borne through the stars.</i> <strong>Johannes Kepler</strong>, Astronomia Nova
-</div>
-
-<p>Welcome to Kepler, the simultaneous Eclipse release for 2013, including
-content from seventy two Eclipse projects. The Eclipse platform and related resources
-can be downloaded from the <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">Eclipse Project downloads page</a>.
-Here are some of the more noteworthy things available in the thirteenth annual release of the Eclipse project SDK.</p>
-
-<blockquote>
-  <ul>
-    <li><a href="eclipse-news-part1.html">New features in the Platform and Equinox</a></li>
-    <li><a href="eclipse-news-part2.html">New features for Java developers</a></li>
-    <li><a href="eclipse-news-part3.html">New APIs in the Platform and Equinox</a></li>
-    <li><a href="eclipse-news-part4.html">New features for plug-in developers</a></li>
-  </ul>
-</blockquote>
-
-</body>
-</html>
diff --git a/platform/4.3/final - SR2/images/additional-info.png b/platform/4.3/final - SR2/images/additional-info.png
deleted file mode 100644
index c8b741b..0000000
--- a/platform/4.3/final - SR2/images/additional-info.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/additional-type-info.png b/platform/4.3/final - SR2/images/additional-type-info.png
deleted file mode 100644
index 3f24504..0000000
--- a/platform/4.3/final - SR2/images/additional-type-info.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/api-parent-not-visible.png b/platform/4.3/final - SR2/images/api-parent-not-visible.png
deleted file mode 100644
index 1003977..0000000
--- a/platform/4.3/final - SR2/images/api-parent-not-visible.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/autostart-all-plugins.png b/platform/4.3/final - SR2/images/autostart-all-plugins.png
deleted file mode 100644
index 3858413..0000000
--- a/platform/4.3/final - SR2/images/autostart-all-plugins.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/autostart-levels.png b/platform/4.3/final - SR2/images/autostart-levels.png
deleted file mode 100644
index 4f00f01..0000000
--- a/platform/4.3/final - SR2/images/autostart-levels.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/bidi.png b/platform/4.3/final - SR2/images/bidi.png
deleted file mode 100644
index 4aa20af..0000000
--- a/platform/4.3/final - SR2/images/bidi.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/category-editor.png b/platform/4.3/final - SR2/images/category-editor.png
deleted file mode 100644
index 9c49163..0000000
--- a/platform/4.3/final - SR2/images/category-editor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/classpath-contributor.png b/platform/4.3/final - SR2/images/classpath-contributor.png
deleted file mode 100644
index 67e2913..0000000
--- a/platform/4.3/final - SR2/images/classpath-contributor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/close-quietly-example.png b/platform/4.3/final - SR2/images/close-quietly-example.png
deleted file mode 100644
index 6c29f05..0000000
--- a/platform/4.3/final - SR2/images/close-quietly-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/combine-strings.png b/platform/4.3/final - SR2/images/combine-strings.png
deleted file mode 100644
index 7765407..0000000
--- a/platform/4.3/final - SR2/images/combine-strings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/content-assist.png b/platform/4.3/final - SR2/images/content-assist.png
deleted file mode 100644
index a3b003c..0000000
--- a/platform/4.3/final - SR2/images/content-assist.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/convert-if-else-to-switch.png b/platform/4.3/final - SR2/images/convert-if-else-to-switch.png
deleted file mode 100644
index be3ea31..0000000
--- a/platform/4.3/final - SR2/images/convert-if-else-to-switch.png
+++ /dev/null
Binary files differ
diff --git "a/platform/4.3/final - SR2/images/convert-to-if-\041-return.png" "b/platform/4.3/final - SR2/images/convert-to-if-\041-return.png"
deleted file mode 100644
index 5cd0b93..0000000
--- "a/platform/4.3/final - SR2/images/convert-to-if-\041-return.png"
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/create-loop-variable.png b/platform/4.3/final - SR2/images/create-loop-variable.png
deleted file mode 100644
index c23d4de..0000000
--- a/platform/4.3/final - SR2/images/create-loop-variable.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/declaration-view-indicating-outofsync.png b/platform/4.3/final - SR2/images/declaration-view-indicating-outofsync.png
deleted file mode 100644
index 4e5e98d..0000000
--- a/platform/4.3/final - SR2/images/declaration-view-indicating-outofsync.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/default-launch-ee.png b/platform/4.3/final - SR2/images/default-launch-ee.png
deleted file mode 100644
index bd17db6..0000000
--- a/platform/4.3/final - SR2/images/default-launch-ee.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/detached-sash.png b/platform/4.3/final - SR2/images/detached-sash.png
deleted file mode 100644
index d904dee..0000000
--- a/platform/4.3/final - SR2/images/detached-sash.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/dom-structure.png b/platform/4.3/final - SR2/images/dom-structure.png
deleted file mode 100644
index dc19e15..0000000
--- a/platform/4.3/final - SR2/images/dom-structure.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/eedescfeature.png b/platform/4.3/final - SR2/images/eedescfeature.png
deleted file mode 100644
index fe8e9f1..0000000
--- a/platform/4.3/final - SR2/images/eedescfeature.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/export-package.png b/platform/4.3/final - SR2/images/export-package.png
deleted file mode 100644
index ec50bb7..0000000
--- a/platform/4.3/final - SR2/images/export-package.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/featureselection.png b/platform/4.3/final - SR2/images/featureselection.png
deleted file mode 100644
index cf9dc8c..0000000
--- a/platform/4.3/final - SR2/images/featureselection.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/gtk3.png b/platform/4.3/final - SR2/images/gtk3.png
deleted file mode 100644
index a9468b4..0000000
--- a/platform/4.3/final - SR2/images/gtk3.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error-Juno.png b/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error-Juno.png
deleted file mode 100644
index 5d4aac9..0000000
--- a/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error-Juno.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error.png b/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error.png
deleted file mode 100644
index 22290a0..0000000
--- a/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error.txt b/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error.txt
deleted file mode 100644
index 9630ec5..0000000
--- a/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error.txt
+++ /dev/null
@@ -1,11 +0,0 @@
-    public static void test(int... a) {
-        System.out.println(Arrays.toString(a));
-    }
-    
-    public static void test(Object... a) {
-        System.out.println(Arrays.toString(a));
-    }
-    
-    public static void main(String[] args) {
-        test(1); // 'test' flagged ambiguous
-    }
diff --git a/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error2.png b/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error2.png
deleted file mode 100644
index 27f715e..0000000
--- a/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error2.txt b/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error2.txt
deleted file mode 100644
index 4a990bd..0000000
--- a/platform/4.3/final - SR2/images/illegal-ambiguous-varargs-error2.txt
+++ /dev/null
@@ -1,6 +0,0 @@
-    public static void foo(int... i) { }
-    public static void foo(double... d) { }
-    
-    public static void main(String[] args) {
-        foo(1, 2, 3); // foo flagged ambiguous
-    }
diff --git a/platform/4.3/final - SR2/images/import-nested.png b/platform/4.3/final - SR2/images/import-nested.png
deleted file mode 100644
index 271a2ad..0000000
--- a/platform/4.3/final - SR2/images/import-nested.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/import-package.png b/platform/4.3/final - SR2/images/import-package.png
deleted file mode 100644
index 7d13527..0000000
--- a/platform/4.3/final - SR2/images/import-package.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/inherit-null-annotations-example.png b/platform/4.3/final - SR2/images/inherit-null-annotations-example.png
deleted file mode 100644
index a51a9da..0000000
--- a/platform/4.3/final - SR2/images/inherit-null-annotations-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/inherit-null-annotations-example2.png b/platform/4.3/final - SR2/images/inherit-null-annotations-example2.png
deleted file mode 100644
index 5f41dd9..0000000
--- a/platform/4.3/final - SR2/images/inherit-null-annotations-example2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/inherit-null-annotations-option.png b/platform/4.3/final - SR2/images/inherit-null-annotations-option.png
deleted file mode 100644
index 322f055..0000000
--- a/platform/4.3/final - SR2/images/inherit-null-annotations-option.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/javadoc-package-names-linked.png b/platform/4.3/final - SR2/images/javadoc-package-names-linked.png
deleted file mode 100644
index 52d6137..0000000
--- a/platform/4.3/final - SR2/images/javadoc-package-names-linked.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/javadoc-view-target.png b/platform/4.3/final - SR2/images/javadoc-view-target.png
deleted file mode 100644
index 25305da..0000000
--- a/platform/4.3/final - SR2/images/javadoc-view-target.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/junit-templates.png b/platform/4.3/final - SR2/images/junit-templates.png
deleted file mode 100644
index 00a9a62..0000000
--- a/platform/4.3/final - SR2/images/junit-templates.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/junit-view-assumptions.png b/platform/4.3/final - SR2/images/junit-view-assumptions.png
deleted file mode 100644
index 4f29f91..0000000
--- a/platform/4.3/final - SR2/images/junit-view-assumptions.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/launch-order.png b/platform/4.3/final - SR2/images/launch-order.png
deleted file mode 100644
index d85ca91..0000000
--- a/platform/4.3/final - SR2/images/launch-order.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/lcd-warnings.png b/platform/4.3/final - SR2/images/lcd-warnings.png
deleted file mode 100644
index 2ade3b5..0000000
--- a/platform/4.3/final - SR2/images/lcd-warnings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/linkColor.png b/platform/4.3/final - SR2/images/linkColor.png
deleted file mode 100644
index c6f4381..0000000
--- a/platform/4.3/final - SR2/images/linkColor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/migration-wizard.png b/platform/4.3/final - SR2/images/migration-wizard.png
deleted file mode 100644
index d19bee9..0000000
--- a/platform/4.3/final - SR2/images/migration-wizard.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/missing-include.png b/platform/4.3/final - SR2/images/missing-include.png
deleted file mode 100644
index 304a810..0000000
--- a/platform/4.3/final - SR2/images/missing-include.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/no-reference.png b/platform/4.3/final - SR2/images/no-reference.png
deleted file mode 100644
index 45d52bc..0000000
--- a/platform/4.3/final - SR2/images/no-reference.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/null-annotations-for-fields-examples.png b/platform/4.3/final - SR2/images/null-annotations-for-fields-examples.png
deleted file mode 100644
index 4276694..0000000
--- a/platform/4.3/final - SR2/images/null-annotations-for-fields-examples.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/null-annotations-for-fields-examples.txt b/platform/4.3/final - SR2/images/null-annotations-for-fields-examples.txt
deleted file mode 100644
index 648bc94..0000000
--- a/platform/4.3/final - SR2/images/null-annotations-for-fields-examples.txt
+++ /dev/null
@@ -1,26 +0,0 @@
-import org.eclipse.jdt.annotation.NonNull;
-import org.eclipse.jdt.annotation.Nullable;
-
-public class NullAnnotatedFields {
-    @NonNull Letter nonNull;
-    @Nullable Letter nullable;
-    String test() {
-        nonNull.print();
-        nullable.print();
-        nonNull = null;
-
-        if (nullable != null)
-            nullable.print(); // protected
-
-        nullable = new Letter();
-        bar();     // spoils protection
-        return nullable.toString();
-    }
-    void bar() {
-       
-    }
-}
-// --- not shown in the screenshot: --- 
-class Letter {
-    void print() {}
-}
\ No newline at end of file
diff --git a/platform/4.3/final - SR2/images/only-include-exported.png b/platform/4.3/final - SR2/images/only-include-exported.png
deleted file mode 100644
index e6cacc2..0000000
--- a/platform/4.3/final - SR2/images/only-include-exported.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/open-resource-buttons.png b/platform/4.3/final - SR2/images/open-resource-buttons.png
deleted file mode 100644
index a741513..0000000
--- a/platform/4.3/final - SR2/images/open-resource-buttons.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/option-syntactic-null-analysis-for-fields.png b/platform/4.3/final - SR2/images/option-syntactic-null-analysis-for-fields.png
deleted file mode 100644
index fbe2422..0000000
--- a/platform/4.3/final - SR2/images/option-syntactic-null-analysis-for-fields.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/override-annotation-code-style.png b/platform/4.3/final - SR2/images/override-annotation-code-style.png
deleted file mode 100644
index 6da2b0a..0000000
--- a/platform/4.3/final - SR2/images/override-annotation-code-style.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/override-annotation-compiler.png b/platform/4.3/final - SR2/images/override-annotation-compiler.png
deleted file mode 100644
index 3b0516c..0000000
--- a/platform/4.3/final - SR2/images/override-annotation-compiler.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/package-javadoc-hover-examples.png b/platform/4.3/final - SR2/images/package-javadoc-hover-examples.png
deleted file mode 100644
index 8a580c9..0000000
--- a/platform/4.3/final - SR2/images/package-javadoc-hover-examples.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/plugin-image-view.png b/platform/4.3/final - SR2/images/plugin-image-view.png
deleted file mode 100644
index bf7815d..0000000
--- a/platform/4.3/final - SR2/images/plugin-image-view.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/pre-fill-package-name.png b/platform/4.3/final - SR2/images/pre-fill-package-name.png
deleted file mode 100644
index 230704e..0000000
--- a/platform/4.3/final - SR2/images/pre-fill-package-name.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/quickassist-for-unused-type-parameter-example.png b/platform/4.3/final - SR2/images/quickassist-for-unused-type-parameter-example.png
deleted file mode 100644
index 5c63e66..0000000
--- a/platform/4.3/final - SR2/images/quickassist-for-unused-type-parameter-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/remediation.png b/platform/4.3/final - SR2/images/remediation.png
deleted file mode 100644
index 72101c3..0000000
--- a/platform/4.3/final - SR2/images/remediation.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/speed.jpg b/platform/4.3/final - SR2/images/speed.jpg
deleted file mode 100644
index f42c47e..0000000
--- a/platform/4.3/final - SR2/images/speed.jpg
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/trim-drag.png b/platform/4.3/final - SR2/images/trim-drag.png
deleted file mode 100644
index 9c79b41..0000000
--- a/platform/4.3/final - SR2/images/trim-drag.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/unresolved-analysis.png b/platform/4.3/final - SR2/images/unresolved-analysis.png
deleted file mode 100644
index b92b1a6..0000000
--- a/platform/4.3/final - SR2/images/unresolved-analysis.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/unused-type-parameter.png b/platform/4.3/final - SR2/images/unused-type-parameter.png
deleted file mode 100644
index 0e6df20..0000000
--- a/platform/4.3/final - SR2/images/unused-type-parameter.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/use-last-page-option.png b/platform/4.3/final - SR2/images/use-last-page-option.png
deleted file mode 100644
index 806f02e..0000000
--- a/platform/4.3/final - SR2/images/use-last-page-option.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/use-scan.png b/platform/4.3/final - SR2/images/use-scan.png
deleted file mode 100644
index f91028e..0000000
--- a/platform/4.3/final - SR2/images/use-scan.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/using-no-reference.png b/platform/4.3/final - SR2/images/using-no-reference.png
deleted file mode 100644
index 51518c8..0000000
--- a/platform/4.3/final - SR2/images/using-no-reference.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/vertical-switcher.png b/platform/4.3/final - SR2/images/vertical-switcher.png
deleted file mode 100644
index 8798efa..0000000
--- a/platform/4.3/final - SR2/images/vertical-switcher.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/whole-word-option.png b/platform/4.3/final - SR2/images/whole-word-option.png
deleted file mode 100644
index ec15556..0000000
--- a/platform/4.3/final - SR2/images/whole-word-option.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final - SR2/images/x-start-on-first-thread.png b/platform/4.3/final - SR2/images/x-start-on-first-thread.png
deleted file mode 100644
index 76ecce0..0000000
--- a/platform/4.3/final - SR2/images/x-start-on-first-thread.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/default_style.css b/platform/4.3/final/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.3/final/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.3/final/eclipse-news-part1.html b/platform/4.3/final/eclipse-news-part1.html
deleted file mode 100644
index 632e26c..0000000
--- a/platform/4.3/final/eclipse-news-part1.html
+++ /dev/null
@@ -1,183 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2013. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Project Kepler - New and Noteworthy</title>
-</head>
-<body>
-<h2>Platform and Equinox</h2>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table class="news" cellpadding="10" cellspacing="0">
-
-  <tr id="detached-sash">
-    <td class="title">Detached windows with sash</td>
-    <td class="content">
-      When you detach a view or editor into its own separate window, it now
-      has all the capabilities of a normal workbench window. They now support multiple stacks of
-      views separated by sashes with arbitrary layouts. The detached parts will remain synchronized
-      with the master window that they were detached from. This is especially handy for people developing
-      with two or more monitors, so they can spread views across several monitors and keep them synchronized.
-		<p><img src="images/detached-sash.png" alt="Detached window with multiple views separated by sash."/></p>
-    </td>
-  </tr>
-
-   <tr id="detect-shared-install-change">
-    <td class="title">Detection of shared install changes</td>
-    <td class="content">
-	  When running in a read-only folder (also known as shared install) and the read-only
-	  installation has changed (e.g. new plugins installed, new version of Eclipse installed), Eclipse 
-	  will now detect this change and warn that your personal additional plugins have been uninstalled.
-	  A migration wizard will then guide you through the steps to re-install your plug-ins, if they are
-	  still compatible with your other installed software.
-	 <p>This wizard is presented in two situations. First, when a read-only installation is being 
-	 changed (i.e. your application is being updated or plugins are added or removed), second when a new read-only 
-	 installation is run for the first time.</p>
-     <p><img src="images/migration-wizard.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="remediation"> 
-    <td class="title">Installation Remediation</td>
-    <td class="content">
-	 In order to help you deal with dependency errors while installing software, the various installation wizards now contain 
-	 a new wizard page. This page, called <b>remediation</b>, proposes various solutions in order to help you proceed 
-	 with the installation, even when the exact change you requested is not possible.
-	 <p>
-	 The picture below shows a screenshot of this page in action. In this particular case the user is trying to install something
-	 that is conflicting with what is installed, and the wizard gives the option to update what is installed so that the installation
-	 can proceed.
-	 </p>
-     <p><img src="images/remediation.png" alt=""/></p>
-    </td>
-  </tr>
-
-  <tr id="gtk3">
-    <td class="title">SWT for GTK3</td>
-    <td class="content">
-      32-bit and 64-bit GTK3 have joined the lineup of supported configurations for which SWT and Eclipse are routinely built. This implementation is currently early access. Everyone is encouraged to download and test these new builds, and to log bugs in <a href="https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Platform">bugzilla</a>.
-      <p>Note to load the SWT GTK3 libraries, you must set an environment variable SWT_GTK3 prior to starting Eclipse. (ex. export SWT_GTK3=1)</p>
-      <p><img src="images/gtk3.png" alt="GTK3 Control Example"/></p>  
-	</td>
-  </tr>
-
-   <tr id="performance">
-    <td class="title">Performance enhancements</td>
-    <td class="content">
-      Significant performance enhancements have been made in the Platform user interface in this release. In particular, some applications
-      that were experiencing slow editor opening, closing, and switching are now much faster. Editor selection changes and the <b>Open Resource</b>
-      dialog have also been made faster. A number of leaks have been addressed to ensure
-      long-running applications don't run out of memory.
-      <p><img src="images/speed.jpg" alt="Speedometer"/><br/>
-	  <small>Photographer: YtseJam Photography / Creative Commons Attribution 2.0</small>
-	  </p>
-	</td>
-  </tr>
-
-  <tr id="trim-drag">
-    <td class="title">Trim dragging</td>
-    <td class="content">
-      You can now drag toolbars to reposition them. 
-      <p><img src="images/trim-drag.png" alt="Dragging a toolbar."/></p>
-      <p>The perspective switcher can also be dragged to the left or right of the window and it will switch to a 
-        vertical orientation.</p>
-	  <p><img src="images/vertical-switcher.png" alt="Dragging perspective switcher to vertical orientation."/></p>
-    </td>
-  </tr>
-
-  <tr id="import-nested">
-    <td class="title">Import nested projects</td>
-    <td class="content">
-      The <b>Import Projects</b> wizard now has an option to continue searching for projects to import
-      recursively within any project it finds. This allows you to import physically nested projects
-      at the same time.
-      <p><img src="images/import-nested.png" alt="Import nested projects."/></p>
-    </td>
-  </tr>
-
-  <tr id="open-resource-buttons">
-    <td class="title">Open Resource dialog enhancements</td>
-    <td class="content">
-      The <b>Open Resource</b> (<b>Ctrl+Shift+R</b>) dialog now offers direct access to the
-      <b>Show In</b> and <b>Open With</b> menus via drop-down buttons. On platforms that
-      support mnemonics, the buttons are also accessible via <b>Alt+W</b> and <b>Alt+H</b>.
-      <p><img src="images/open-resource-buttons.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="whole-word-option">
-    <td class="title">Whole word option on File Search page</td>
-    <td class="content">
-     The <b>File Search</b> page now allows to search for words via a new option:
-     <p><img src="images/whole-word-option.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="use-last-page-option">
-    <td class="title">Open Search dialog on last used page</td>
-    <td class="content">
-     The Search dialog can now be configured to open on the last used page, instead of 
-     computing the best matching page based on the current selection:
-     <p><img src="images/use-last-page-option.png" alt=""/></p>
-    </td>
-  </tr>
-
-  <tr id="launch-dialog-warnings">
-    <td class="title">Launch configuration dialog can show warnings</td>
-    <td class="content">
-      Previously, contributors could only set an 'ok' or an 'error' state in their launch configuration tags / groups. Now,
-      contributors can set a warning state with a message for their tabs / groups - possibly warning users about set options
-      that might be problematic, but do not necessarily need to prevent launching.
-      <p><img src="images/lcd-warnings.png" alt="Launch configuration dialog showing warning message / state"/></p>
-    </td>
-  </tr>
-  
-  <tr id="x-start-on-first-thread">
-    <td class="title">Option to omit <span style="letter-spacing:-0.05em;">-XstartOnFirstThread</span></td>
-    <td class="content">
-      If you are launching an SWT program on Mac OS X, you can now selectively add / remove the <code>-XstartOnFirstThread</code> VM argument
-      in the event your VM does not support it. This option can be configured per launch configuration and is available on the standard Arguments
-      tab for Java configurations (Java Application, Eclipse, etc.).
-      <p><img src="images/x-start-on-first-thread.png" alt="New VM preference allowing users to selectively add the -XstartOnFirstThread argument per-configuration"/></p>
-    </td>
-  </tr>
-
-  <tr id="ant-augment">
-    <td class="title">Support for the Ant augment task</td>
-    <td class="content">
-      The Ant editor now has support for the Ant
-      <a href="http://ant.apache.org/manual/Tasks/augment.html">
-      <code>augment</code></a> task.  
-    </td>
-  </tr>
-  
-  <tr id="stop-thread">
-    <td class="title">Stop thread from OSGi console</td>
-    <td class="content">
-      If a bad plug-in runs into an endless loop, then you previously had to kill the whole Eclipse process.
-      Now, you can launch Eclipse with <code>-console [[host:]port]</code> to get a safety ring.
-      If you're then stuck in an endless loop and Eclipse doesn't respond any more, you can just execute
-      <pre>osgi&gt; threads stop main</pre>
-      at the OSGi prompt. This will send an IllegalStateException to the "main" thread.
-      This is usually enough to stop the endless loop, but keep the Eclipse workbench running.
-      <p>If you don't want to keep a console window around, you can pass a port number (e.g. 12345) after
-      the <code>-console</code> command line argument and later use <code>telnet localhost:12345</code> to connect.</p>
-    </td>
-  </tr>
-
-  <!-- ****************** END OF N&N TABLE ****************** -->
-</table>
-
-<p align="center"><font color="#808080">Previous</font>&nbsp;&nbsp;&nbsp;&nbsp; <a href="eclipse-news-part2.html">Next</a></p>
-</body>
-</html>
diff --git a/platform/4.3/final/eclipse-news-part2.html b/platform/4.3/final/eclipse-news-part2.html
deleted file mode 100644
index 91d4729..0000000
--- a/platform/4.3/final/eclipse-news-part2.html
+++ /dev/null
@@ -1,478 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2013. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Project Kepler - New and Noteworthy</title>
-</head>
-<body>
-<h2>Java development tools</h2>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-
-<table class="news" cellpadding="10" cellspacing="0">
-
-  <!-- ******************* Java Editor ************************************* -->
-  <tr>
-    <td id="JavaEditor" class="section" colspan="2">
-    <h2>Java Editor </h2>
-    </td>
-  </tr>
-  
-  <tr id="convert-if-else-to-switch">
-    <td class="title">New 'Convert if-else to switch' Quick Assist</td>
-    <td class="content">
-      The new <b>Convert 'if-else' to 'switch'</b> quick assist (<b>Ctrl+1</b>) allows you to convert an if-else statement to 
-      an equivalent switch statement:
-      <p><img src="images/convert-if-else-to-switch.png" alt=""/></p>
-      
-      This quick assist is the reverse of the existing <b>Convert 'switch' to 'if-else'</b> quick assist.
-    </td>
-  </tr>  
-    
-  <tr id="convert-to-if-return">
-    <td class="title">'Convert to if-!-return' Quick Assist</td>
-    <td class="content">
-     Ever encountered a long <code>if</code> statement that can be safely inverted to an early return, so that you can ignore the code that follows, and make it easier to understand? 
-     Now, you can just use a quick assist <b>(Ctrl+1)</b> on the <code>if</code> statement to do this refactoring:
-     <p><img src="images/convert-to-if-!-return.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="create-loop-variable">
-    <td class="title">Quick Fix to create 'for' loop variable</td>
-    <td class="content">
-      The new <b>Create loop variable</b> quick fix corrects an incomplete 'for' loop
-      by adding the type of the loop variable:
-      <p><img src="images/create-loop-variable.png" alt="Corrects 'for (e: elements) {}' to 'for (ElementType e: elements) {}'"/></p>
-    </td>
-  </tr>
-          
-  <tr id="combine-strings">
-    <td class="title">Quick Assist to combine Strings</td>
-    <td class="content">
-      The new <b>Combine to single String</b> quick assist (<b>Ctrl+1</b>) replaces String concatenations
-      with a single String literal:
-      <p>
-        <img src="images/combine-strings.png" alt="String s = &quot;Delete &quot; + &quot;two&quot; + &quot; files?&quot; // becomes: String s = &quot;Delete two files?&quot;"/>
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="Quick-Assist-for-unused-type-parameters">
-    <td class="title">Quick Assist for unused type parameters</td>
-    <td class="content">
-      The Java editor now provides a quick assist (<b>Ctrl+1</b>) to remove or document unused type parameters:
-      <p><img src="images/quickassist-for-unused-type-parameter-example.png" alt=""/></p>
-    </td>
-  </tr>
-  
-  <tr id="proposals-without-prefix">
-    <td class="title">Template and keyword proposals without prefix</td>
-    <td class="content">
-      Content assist now proposes templates and keywords without needing a prefix first:
-      <p><img src="images/content-assist.png" alt=""/></p>
-    </td>
-  </tr>
-       
-  <tr id="remove-type-arguments">
-    <td class="title">Remove type arguments after content assist</td>
-    <td class="content">
-     Ever encountered a case where content assist added type arguments for a generic type, but you do not want them
-     because you need the <code>.class</code> literal or you want to invoke a static method?
-     Now, rather than deleting all the arguments manually, 
-     you can just delete the '<code>&lt;</code>' and that will remove the entire text up to '<code>&gt;</code>'.
-    </td>
-  </tr>
-  
-  <tr id="semicolon-appended-for-void-methods">
-    <td class="title">Content assist appends ';' to void methods</td>
-    <td class="content">
-    If a void method is selected during content assist, then a semicolon is now automatically
-    appended at the end of the method invocation.
-    </td>
-  </tr>
-  
-  <tr id="semicolon-key-inserts-method">
-    <td class="title">Use ';' key to insert method invocation</td>
-    <td class="content">
-    Irrespective of the return type of a method, you can now use the semicolon (<b>;</b>) key to select any method invocation proposal
-    from the content assist popup. The '<code>;</code>' will be appended at the end of the method invocation.
-    </td>
-  </tr>  
-  
-  <!-- ******************* Java Compiler ************************************* -->
-  <tr>
-    <td id="JavaCompiler" class="section" colspan="2">
-    <h2>Java Compiler</h2>
-    </td>
-  </tr>
-  
-  <tr id="content-assist-TL_CONSTRUCTOR_START">
-    <td class="title">New API to indicate content assist requested on the start of a constructor</td>
-    <td class="content">
-      org.eclipse.jdt.core.CompletionContext.TL_CONSTRUCTOR_START:
-      <pre>
-	  /**
-	   * The completed token is the first token of a constructor
-	   * invocation expression.
-	   * e.g.
-	   * 
-	   * public class X {
-	   *   public void bar() {
-	   *     new Foo| // completion occurs at |
-	   *   }
-	   * }
-	   */
-	</pre>
-    </td>
-  </tr>
-  
-   <tr id="tolerateIllegalAmbiguousVarargsInvocation">
-    <td class="title">Force Eclipse to compile (illegal) ambiguous varargs code</td>
-    <td class="content"> JDK 6 and below had a bug and considered the code below legal.
-	However, this bug was fixed in JDK 7 and the code now reports an ambiguous invocation error at the call site for test(..).
-	Eclipse Juno followed and fixed this across all compliance levels:
-	<p><a href="images/illegal-ambiguous-varargs-error.txt"><img src="images/illegal-ambiguous-varargs-error.png" alt="follow link for source"/></a></p>
-	<p>If you still want the above code to compile in compliance &lt; 1.7, to mimic JDK 6 or below, you can use the
-	system property <b>tolerateIllegalAmbiguousVarargsInvocation</b> to force Eclipse to tolerate such ambiguous varargs cases.
-	This property can e.g. be set in the eclipse.ini file after the -vmargs setting:</p>
-	<pre><code>...
-        	 -vmargs
-			-DtolerateIllegalAmbiguousVarargsInvocation=true
-			...</code></pre>
-	<p><i>Note</i>: With this setting, Eclipse also	mimics JDK 6 and below in raising an error in other cases that are legal in both JDK 7 and Eclipse:</p>
-	<p><a href="images/illegal-ambiguous-varargs-error2.txt"><img src="images/illegal-ambiguous-varargs-error2.png" alt="follow link for source"/></a></p>
-	</td>
-  </tr>
-
-  <tr id="new-batch-compiler-options">
-    <td class="title">New batch compiler options</td>
-    <td class="content"> If you use the ECJ batch compiler using the command line or Ant tasks, you can now configure the following options which previously could only be set through
-	the <b>Preferences &gt; Java &gt; Compiler &gt; Errors/Warnings</b> page:
-	<ul>
-      <li>invalidJavadoc: set all warnings for malformed Javadoc tags</li>
-      <li>invalidJavadocTag: validate Javadoc tag arguments</li>
-      <li>invalidJavadocTagDep: validate deprecated references in Javadoc tag args</li>
-      <li>invalidJavadocTagNotVisible: validate non-visible references in Javadoc tag args</li>
-      <li>invalidJavadocVisibility(&lt;visibility&gt;): specify visibility modifier for malformed Javadoc tag warnings</li>
-      <li>missingJavadocTags: enable detection of missing Javadoc tags</li>
-      <li>missingJavadocTagsOverriding: detect missing Javadoc tags in overriding methods</li>
-      <li>missingJavadocTagsMethod: detect missing Javadoc tags for method type parameter</li>
-      <li>missingJavadocTagsVisibility(&lt;visibility&gt;): specify visibility modifier for missing Javadoc tags warnings</li>
-      <li>missingJavadocComments: detect missing Javadoc comments</li>
-      <li>missingJavadocCommentsOverriding: detect missing Javadoc tags in overriding methods</li>
-      <li>missingJavadocCommentsVisibility(&lt;visibility&gt;): specify visibility modifier for missing Javadoc comments warnings</li>
-      <li>nullAnnotConflict: detect conflict between null annotation specified and nullness inferred. Is effective only with nullAnnot option enabled</li>
-      <li>nullAnnotRedundant: detect redundant specification of null annotation. Is effective only with nullAnnot option enabled</li>
-      <li>nullUncheckedConversion: detect unchecked conversion from non-annotated type to @NonNull type. Is effective only with nullAnnot option enabled</li>
-      <li>unusedParam: detect unused parameter</li>
-      <li>unusedParamOverriding: detect unused parameter for overriding method</li>
-      <li>unusedParamImplementing: detect unused parameter for implementing method</li>
-      <li>unusedParamIncludeDoc: detect unused parameter documented in comment tag</li>
-      <li>unusedThrownWhenOverriding: detect unused declared thrown exception in overriding method</li>
-      <li>unusedThrownIncludeDocComment: detect unused declared thrown exception, documented in a comment tag</li>
-      <li>unusedThrownExemptExceptionThrowable: detect unused declared thrown exception, exempt Exception and Throwable</li>
-	</ul>
-	<p> For more information on using batch compiler options, please refer to <b>Help &gt; Java Development User Guide &gt; Tasks &gt; Compiling Java Code &gt; Using the batch compiler</b>.</p>
-    </td>
-  </tr>
-      
-  <tr id="unused-type-parameter">
-    <td class="title">Option to omit @Override for interface methods</td>
-    <td class="content">
-      Eclipse can add <code>@Override</code> annotations for overriding methods:
-      <p>
-        <img src="images/override-annotation-code-style.png" alt="Code Style preference page"/>
-      </p>
-      <p>
-        If your code uses Java 1.6 or higher, the <code>@Override</code> annotation is also added to
-        methods that override an interface method. If you don't want to use <code>@Override</code>
-        in this case, then follow the link and disable the corresponding compiler option:
-      </p>
-      <p>
-        <img src="images/override-annotation-compiler.png" alt="Errors/Warnings preference page, checkbox 'Include implementations of interface methods (1.6 or higher)'"/>
-      </p>
-      <p>
-        You may also want to enable the diagnostic for Missing '@Override' annotation.   
-      </p>
-    </td>
-  </tr>
-    
-  <tr id="detection-unused-type-parameter">
-    <td class="title">Detection of unused type parameters</td>
-    <td class="content">
-      The compiler can now detect unused type parameters:
-      <p>
-        <img src="images/unused-type-parameter.png" alt=""/>
-      </p>
-      <p>
-        The <b>Unused type parameter</b> diagnostic is set to Ignore by default and can be enabled on the 
-		<b>Java &gt; Compiler &gt; Errors/Warnings</b>
-		preference page.
-      </p>
-    </td>
-  </tr>  
-  
-  <tr id="inherit-null-annotations">
-    <td class="title">Option to inherit null annotations</td>
-    <td class="content">
-        JDT has a new option controlling how to interpret null annotations in the presence of inheritance.
-        This should facilitate the migration towards null annotations in projects with
-        mixed code ownership.
-      <p>For the sake of code readability, JDT expects null annotations of an overridden
-        method to be repeated in overriding methods. In the following example the analysis
-        normally complains that <code>arg</code> is not annotated in <code>ClientClass</code>,
-        which means, this class doesn't formally conform to the contract of its super-interface:
-      </p>
-      <p><img title="Example for inheritance of null annotations" src="images/inherit-null-annotations-example.png" 
-          alt="Example for inheritance of null annotations"/></p>
-      <p>Starting with 4.3M4 this behavior can be changed by selecting the option
-        <strong>Inherit null annotations</strong>:
-      </p>
-      <p><img title="Option for inheritance of null annotations" src="images/inherit-null-annotations-option.png"
-           alt="Option for inheritance of null annotations"/></p>
-      <p>In this new mode the analysis implicitly fills in all missing annotations
-        in overriding methods and uses the annotations from the overridden method.
-        In the above example the error will go away, and analysis concludes that the
-        code is actually safe, which is likely when the contract had already been
-        defined in the javadoc comment and the implementor actually adheres to that
-        contract. If, on the other hand, the implementation does not comply with the
-        inherited specification, new errors will be reported as shown below:
-      </p>
-      <p><img title="Negative example for inheritance of null annotations" src="images/inherit-null-annotations-example2.png"
-          alt="Negative example for inheritance of null annotations"/></p>
-      <p>If inheritance of null annotations encounters any ambiguity or conflict
-        the analysis falls back to requiring explicit annotations.
-      </p>
-    </td>
-  </tr>
-
-  <tr id="null-annotations-for-fields">
-    <td class="title">Null annotations for fields</td>
-    <td class="content">
-      The annotation-based null analysis &mdash; first released with Eclipse Indigo &mdash; has been extended
-      to apply also to fields. If enabled, this analysis will now detect the following problems
-      concerning any field annotated with <code>@NonNull</code>:
-      <ul>
-      <li>If the field is not properly initialized to a non-null value.</li>
-      <li>If a value is assigned to the field that is not known to be non-null.</li>
-      </ul>
-      <p>In return to these obligations, dereferencing a <code>@NonNull</code> field is regarded as always safe.
-      </p>
-      <p>If a field is marked as <code>@Nullable</code>, generally every direct dereference
-        of the field is flagged as a potential null pointer access. Even a null check for such a field is not
-        a perfect protection due to dangers of side effects, effects via aliased references, and concurrency.</p>
-      <p>As a compromise between safety and convenience, the compiler can be configured to apply
-        <strong>"syntactic null analysis for fields"</strong>.
-        With this option enabled, the compiler syntactically recognizes
-        a narrow range of code patterns where a null-check of a field is <em>directly</em> followed by
-        a dereference or an assignment to a <code>@NonNull</code> variable. For these particular situations,
-        no problem will be reported.</p>
-      <p>In the following example, the check in line 12 properly protects the access in line 13, whereas
-        the knowledge that field <code>nullable</code> holds a non-null value (in line 15) is spoiled by
-        the intermediate statement in line 16:</p>
-	  <p><a href="images/null-annotations-for-fields-examples.txt"><img src="images/null-annotations-for-fields-examples.png" alt=""/></a></p>
-      <p>This is the option that enables the syntactic analysis (under the heading <strong>Java Compiler &gt; Errors/Warnings</strong>):</p>
-	  <p><img src="images/option-syntactic-null-analysis-for-fields.png" alt=""/></p>
-	</td>
-  </tr>   
- 
-  <tr id="close-quietly">
-    <td class="title">Leak analysis respects well-known utilities</td>
-    <td class="content">
-        JDT's analysis for resource leaks has been made aware of well known utilities
-        from google and apache libraries.
-      <p>Generally, this analysis looks for <code>close()</code> method calls
-        directly on a resource (any value of type <code>Closeable</code>).
-        However, in order to reduce boilerplate exception handling, several libraries
-        are providing methods like <code>closeQuietly(Closeable)</code>.
-        Previously, the analysis would complain about the missing call to <code>close()</code>
-        as shown below:
-      </p>
-      <p><img title="Example for close quietly" src="images/close-quietly-example.png"
-          alt="Example for close quietly"/></p>
-      <p>This warning is not relevant and will no longer be reported.
-        To achieve this, JDT now hardcodes a (short) white list of functions that
-        are known to safely close a given resource.
-      </p>
-    </td>
-  </tr>
-  
-  <!-- ******************* Java Views and Dialogs ************************************* -->
-  <tr>
-    <td id="JavaViews" class="section" colspan="2">
-    <h2>Java Views and Dialogs</h2>
-    </td>
-  </tr>
-  
-  <tr id="pre-fill-package-name">
-	<td class="title">Pre-filling package name in creation wizards</td>
-	<td class="content">
-      All the type and package creation wizards now pre-fill the package name
-      if a suitable package name can be suggested for the selected project or source folder:
-      <p><img src="images/pre-fill-package-name.png" alt=""/></p>
-      <p>The suggested package name is the name of the project if the source folder does not contain any package
-      and if the project name is a valid package name.
-      In case of type creation wizards, if the source folder contains exactly one package then the name of that package
-      is used as the suggested package name.</p>
-   </td>
-  </tr>
-  
-   <tr id="content-assist-additional-info-in-debug-views">
-    <td class="title">Content assist shows Javadoc in Display, Expressions and Variables view</td>
-    <td class="content">
-        Content assist in the Display, Expressions and Variables view now shows Javadoc:
-		<p><img src="images/additional-info.png" alt="Screenshot showing Javadoc when doing content assist"/></p>
-	</td>
-  </tr>
-  
-  <tr id="javadoc-view-target">
-    <td class="title">Javadoc view resolves enclosing method call and keeps last target</td>
-    <td class="content">
-      The <b>Javadoc</b> and <b>Declaration</b> views now try to find the enclosing method call
-      if the selection or caret position doesn't resolve to a valid Java element:
-      <p>
-        <img src="images/javadoc-view-target.png" alt="'String.copyValueOf(data, offset, count)', with 'data' selected."/>
-      </p>
-      Furthermore, they keep the last resolved target element even if no new target can be resolved.
-    </td>
-  </tr>
-  
-  <tr id="Support-for-package-Javadoc-in-Javadoc-hover-and-view">
-    <td class="title">Support for package Javadoc in Javadoc hover and view</td>
-    <td class="content">
-      The Javadoc hover and view now display package Javadoc from either the
-      <code style="white-space:nowrap;">package-info.java</code> or the <code>package.html</code> file:
-      <p><img src="images/package-javadoc-hover-examples.png" alt=""/></p>
-    </td>
-  </tr>
-    
-  <tr id="linked-Javadoc-package-names">
-   <td class="title">Package names are linked in Javadoc hover and view</td>
-   <td class="content">
-     You can now click individual package names displayed in the header of the Javadoc hover or the Javadoc view to see the package Javadoc:
-     <p><img src="images/javadoc-package-names-linked.png" alt=""/></p>
-   </td>
-  </tr>  
-  
-   <tr id="InfoViews-should-indicate-when-linking-is-outOfSync">
-   <td class="title">Javadoc and Declaration view indicate when out of sync</td>
-   <td class="content">
-     The Javadoc and Declaration view now indicate when their content is no longer in sync with the current selection:
-     <p><img src="images/declaration-view-indicating-outofsync.png" alt=""/></p>
-   </td>
-  </tr>
-  
-  <!-- *********************** Debug ******************************** -->
-  <tr>
-    <td id="Debug" class="section" colspan="2">
-    <h2>Debug</h2>
-    </td>
-  </tr>  
-     
-  <tr id="debug-improved-generics-eval">
-   <td class="title">Improved evaluation of generics while debugging</td>
-   <td class="content">
-     Significant improvements have been made in the debug evaluation engine to support the use of
-     generics. This impacts the use of conditional breakpoints, the display view, the expressions view,
-     and the inspect/display/execute actions. Previously, evaluations acting on classes with generics
-     would sometimes encounter compilation errors.
-   </td>
-  </tr>
-   
-  <tr id="debug-ext-source-api">
-   <td class="title">API to contribute location information for non-standard JRE / JDK libraries</td>
-   <td class="content">
-     JDT Debug now provides an extension point <code>org.eclipse.jdt.launching.libraryLocationResolvers</code>
-     that you can use to contribute location information for non-standard JRE / JDK libraries.  For example,
-     this extension point can be used to provide Javadoc and source locations for JARs in the ext location
-     of a JRE.
-     <p>
-     Extenders must provide an implementation of <code>org.eclipse.jdt.launching.ILibraryLocationResolver</code>
-     which can provide package roots, source paths, Javadoc locations and index locations for a library.
-     </p> 
-   </td>
-  </tr>  
-  
-  <tr id="xml-dom-structure">
-    <td class="title">XML DOM logical structures</td>
-    <td class="content">
-      JDT now provides a default logical structure for XML DOMs, which can be used during debugging to view the children and attributes of a node as simple arrays:
-      <p>
-      <img src="images/dom-structure.png" alt="Variables view showing the XML DOM logical structure"/>
-      </p>
-    </td>
-  </tr>
-
-   <tr id="only-include-exported-entries">
-    <td class="title">Global preference to include exported entries during launching</td>
-    <td class="content">
-      A new global preference has been added so you can only allow exported classpath entries to be used during launching. Previously, this 
-      was only customizable per launch configuration on the default classpath entry on the Java Classpath tab. The new preference does not affect 
-      launch configuration data, so no migration is needed.
-      
-      <p>
-      The new preference can be found on the <b>Java &gt; Debug</b> preference page.</p>
-      <p><img src="images/only-include-exported.png" alt="New global preference to only include exported classpath entries"/></p>
-      
-    </td>
-  </tr>
-
-  <!-- ******************* JUnit ************************************* -->
-  <tr>
-    <td id="JUnit" class="section" colspan="2">
-    <h2>JUnit</h2>
-    </td>
-  </tr>
-    
-  <tr id="junit-4-11">
-    <td class="title">Only one JUnit (4.11)</td>
-    <td class="content">
-        The org.junit bundle has been updated to
-        <a href="http://htmlpreview.github.com/?https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.html">JUnit 4.11</a>.
-      <p>
-        At the same time, our good old friend org.junit_3.8.2 has been retired, and the org.junit4 compatibility bundle
-        has also been removed. Your <code>Require-Bundle:</code> entries should just point to
-        <code>org.junit;bundle-version="4.11.0"</code> (or an earlier version, if you like).
-      </p>
-      <p>Note that JUnit 4 still contains the JUnit 3 APIs. If you need org.junit_3.8.2 back for
-        whatever reason, you can still get it from <a href="http://download.eclipse.org/tools/orbit/downloads/">Orbit</a>.
-      </p>
-    </td>
-  </tr>
-
-  <tr id="test-templates">
-    <td class="title">JUnit test templates</td>
-    <td class="content">
-      The JUnit test templates have been renamed to show the JUnit 4 template before the JUnit 3 template:
-      <p><img src="images/junit-templates.png" alt="'test' for JUnit 4; 'test3' for JUnit 3"/></p>
-    </td>
-  </tr>
-  
-  <tr id="junit-view-assumptions">
-    <td class="title">JUnit view shows assumption failures</td>
-    <td class="content">
-      The JUnit view now counts <code>@Ignore</code>d tests and tests that didn't meet
-      an assumption as "skipped' tests. The skipped tests also got new icons, and
-      tests with an assumption failure no longer get the 'passed' checkmark:
-      <p><img src="images/junit-view-assumptions.png" alt="Test cases using @Ignore and Assume.assumeFalse(true)"/></p>
-    </td>
-  </tr>
- 
-    <!-- ****************** END OF N&N TABLE ****************** -->
-</table>
-
-<p align="center"><a href="eclipse-news-part1.html">Previous</a>&nbsp;&nbsp;&nbsp;&nbsp; <a href="eclipse-news-part3.html">Next</a></p>
-</body>
-
-</html>
diff --git a/platform/4.3/final/eclipse-news-part3.html b/platform/4.3/final/eclipse-news-part3.html
deleted file mode 100644
index 05c71c4..0000000
--- a/platform/4.3/final/eclipse-news-part3.html
+++ /dev/null
@@ -1,143 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2013. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Project Kepler - New and Noteworthy</title>
-</head>
-<body>
-
-<h2>Platform and Equinox API</h2>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table class="news" cellpadding="10" cellspacing="0">
-<tbody>
-  <!-- ******************** Platform ********************** -->
-  <tr>
-    <td id="Platform" class="section" colspan="2"><h2>Platform Changes</h2></td>
-  </tr>
-  
-  <tr id="e4-api">
-    <td class="title">Initial Eclipse 4 API released</td>
-    <td class="content">
-      The first set of official API based on the new Eclipse Platform 4 architecture is now available. 
-      This is the first step in allowing developers to use the new simpler and more powerful mechanisms 
-      to build Eclipse plug-ins and applications.
-    <p>
-      This API is comprised of two basic concepts:
-    </p><p>
-      <b>The user interface model</b>: The content of this model describes the structure of the user interface.
-      The Eclipse Platform reacts to changes in this model by updating the presentation, and the complete
-      model is now available through the new API.
-    </p><p>
-      Note that the model represents everything on the screen and these elements can be modified
-      by your code (see the example below).
-    </p><p>
-      <b>IEclipseContext / Dependency Injection (DI)</b>: Contexts are containers of UI runtime state
-      including all the available services. The typical Eclipse Platform 4 pattern is that contributions
-      are created and configured through dependency injection based on state and services found in the local
-      context for that model element.
-    </p><p>
-      Here are a few links to more information about the UI Model, the services and DI (the Javadoc and supporting
-      Eclipse documentation will be available before Kepler is released):
-    </p>
-    <ul>
-      <li><a href="http://www.eclipsecon.org/2013/sites/eclipsecon.org.2013/files/FormalAPI.pdf">EclipseCon 2013 API Slides</a></li>
-      <li><a href="http://www.vogella.com/articles/EclipseRCP/article.html">Lars' RCP Tutorial</a></li>
-      <li><a href="http://www.vogella.com/articles/Eclipse4Services/article.html">Lars' Services Tutorial</a></li>
-      <li><a href="http://eclipsesource.com/blogs/2013/04/18/eclipse-4-e4-tutorial-behavior-annotations/">Jonas Helming's DI Tutorials</a></li>
-    </ul>
-    <p>
-      There is quite a lot of information already available for Eclipse Platform 4. While parts of the API are just being
-      formalized now, most of the concepts and API existed in provisional form in previous Eclipse 4 releases.
-    </p><p>
-      Just to give a taste of what working in a modeled UI is all about, here's a code snippet showing
-      how to get a 'standard' Command handler to toggle the visibility of the 'Quick Access' text field
-      that appears in the top trim. First we gain access to the model by getting the MApplication as a
-      'service'. Form there we can access the EModelService and use it to find the model element
-      representing the search in the UI. Then it's just a simple matter of toggling the element's
-      'toBeRendered' flag to get it to (dis)appear.
-    </p>
-    <pre>
-public Object execute(ExecutionEvent e) throws ExecutionException {
-  IWorkbenchWindow window = HandlerUtil.getActiveWorkbenchWindowChecked(e);
-  MApplication theApp = (MApplication) window.getService(MApplication.class);
-  MWindow activeWin = theApp.getSelectedElement();
-  EModelService ms = activeWin.getContext().get(EModelService.class);
-  EPartService ps = activeWin.getContext().get(EPartService.class);
-  MToolControl search = (MToolControl) ms.find("SearchField", activeWin);
-  if (search != null) {
-    search.setToBeRendered(!search.isToBeRendered());
-    window.getShell().layout(true, true);
-  }
-  return null;
-}
-      </pre>
-    </td>
-  </tr>
-
-  <tr id="ua-lucene">
-    <td class="title">Migrated to Lucene 3.5</td>
-    <td class="content">
-      The Eclipse platform help system has migrated from Lucene 2.9.1 to Lucene 3.5.
-      This change brings improved performance and many bug fixes in help search.
-      Some old help system API related to Lucene has been changed or removed as part
-      of this fix. Refer to the platform 4.3 migration guide for more details.
-    </td>
-  </tr>  
-  
-  <tr id="ant184">
-    <td class="title">Platform updated to Ant 1.8.4</td>
-    <td class="content">
-      The platform has been updated to use Apache Ant version 1.8.4. To see what is new in version 1.8.4 you can
-      check the <a href="http://apache.mirrors.tds.net/ant/README.html">Apache Ant what's new</a>.
-    </td>
-  </tr> 
-
-
-  <!-- *********************** SWT *********************** -->
-  <tr>
-    <td id="SWT" class="section" colspan="2"><h2>SWT Changes</h2></td>
-  </tr>
-
-  <tr id="xulrunner64">
-    <td class="title">XULRunner on 64-bit Windows</td>
-    <td class="content">The browser widget now supports the embedding of XULRunner on Windows x86_64.</td>
-  </tr> 
-
-  <tr id="bidi">
-    <td class="title">New SWT color constant for hyperlinks</td>
-    <td class="content">
-     A new constant (SWT_COLOR_LINK_FOREGROUND) has been added that returns the native color of hyperlinks on all platforms.
-     <p><img src="images/linkColor.png" alt=""/></p>
-    </td>
-  </tr>
-    
-  <tr id="linkColor">
-    <td class="title">BIDI Text Direction</td>
-    <td class="content">
-     New API has been added to allow text direction to be set independent of the widget orientation.
-     Note that this API is currently only implemented on Windows. 
-     <p>For more info see <a href="http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/examples/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet364.java">Snippet 364</a>.
-     </p>
-     <p><img src="images/bidi.png" alt=""/></p>
-    </td>
-  </tr>
-
-  </tbody>
-<!-- ****************** END OF N&N TABLE ****************** -->
-</table>
-
-<p align="center"><a href="eclipse-news-part2.html">Previous</a>&nbsp;&nbsp;&nbsp;&nbsp; <a href="eclipse-news-part4.html">Next</a></p>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/platform/4.3/final/eclipse-news-part4.html b/platform/4.3/final/eclipse-news-part4.html
deleted file mode 100644
index 2bd4523..0000000
--- a/platform/4.3/final/eclipse-news-part4.html
+++ /dev/null
@@ -1,327 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) Eclipse contributors and others 2013. This page is made available under license. For full details, see the LEGAL section in the documentation that contains this page."/>
-<meta http-equiv="Content-Language" content="en-us"/>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css"/>
-<style type="text/css">
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-</style>
-<title>Eclipse Project Kepler - New and Noteworthy</title>
-</head>
-<body>
-<div style="font-size: 20px; font-weight: bold;">Plug-in Development Environment</div>
-
-<!-- ****************** START OF N&N TABLE ****************** -->
-<table class="news" cellpadding="10" cellspacing="0">
-  <tbody>
-  
-  <!-- ******************** APITools ********************** -->
-  <tr>
-    <td id="APITools" class="section" colspan="2"><h2>API Tools</h2></td>
-  </tr>
-
-  <tr id="ee-desc-feature">
-    <td class="title">New API Tools EE descriptions feature</td>
-    <td class="content">
-      The API Tools Execution Environment descriptions are now supplied on the Eclipse update sites as a single
-      installable feature.  The feature includes the descriptions for all supported execution environments.
-      
-       <p><img src="images/eedescfeature.png" alt="New EE Desc feature on update sites"/></p> 
-    </td>
-  </tr>
-  
-    <tr id="noreference-types">
-    <td class="title">API Tools allows @noreference Javadoc tag on types</td>
-    <td class="content">
-      API Tools now allows the use of the <code>@noreference</code> Javadoc tag on types (classes, interfaces,
-      annotations and enums).
-      <p><img src="images/no-reference.png" alt="Type defining noreference Javadoc tag"/></p>
-      <p>Placing this tag restricts the API so that any reference to that type or its members
-      will be flagged as invalid API use.</p>
-      <p><img src="images/using-no-reference.png" alt="Class trying to reference a type marked as noreference"/></p>
-      <p>
-      To mark a type in an API package as not being API, tag it as <code>@noreference</code>,
-      <code>@noextend</code> and <code>@noinstantiate</code> (or <code>@noimplement</code>).  This ensures that
-      no client can access it via valid API and the type could later be removed.
-      </p>
-    </td>
-  </tr>
-  
-    <tr id="api-tags-check-visibility">
-    <td class="title">API Tools Javadoc tags check visibility</td>
-    <td class="content">
-      A member that is not publicly visible, such as a method or field marked private, is not part 
-      of API.  Any API Tools Javadoc tags on it are invalid.  Now, API Tools will also check if a
-      member is not visible because of the visibility of an enclosing type.  If the member is not visible,
-      any tags on it will be considered invalid.
-      <p><img src="images/api-parent-not-visible.png" alt="Javadoc tag flagged as invalid because member is not visible"/></p>
-      <p>
-      Tag validation is turned off by default.  To turn it on for your API Tools enabled project, open 
-      <b>Project Properties > Plug-in Development > API Errors/Warnings</b>.  Set 
-      <b>API Use > General > Unsupported use of API Javadoc tags</b> to <code>Warning</code> or <code>Error</code>.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="support-pre-osgi-bundles">
-    <td class="title">API Tools has limited support for pre-OSGi Eclipse plug-ins</td>
-    <td class="content">
-      Eclipse plug-ins created before 3.1 did not contain an OSGi bundle manifest.  API Tools
-      can now convert the pre-OSGi plug-ins to valid components in an API baseline.  This allows
-      analysis, use and freeze scans to process plug-ins that depend on pre-OSGi plug-ins instead
-      of failing to resolve.
-      <p><img src="images/use-scan.png" alt="Use scan launch configuration with pre-OSGi plug-ins"/></p>
-      <p>
-      An OSGi runtime is required to do the conversion.  Tasks run using Eclipse AntRunner
-      or the API Use Report external tools launch configuration can convert the plug-ins.  Tasks
-      run from the command line Ant runner will skip pre-OSGi plug-ins.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="api-unresolved-bundles">
-   <td class="title">API Tools Analysis and Freeze tasks can run with unresolved bundles</td>
-   <td class="content">
-	 The API Tools <b>Analysis</b> and <b>API Freeze</b> Ant tasks will now process bundles
-	 with resolver errors such as missing dependencies.  This means you can now get analysis results
-	 for an incomplete product.
-	 <p>
-     The Ant tasks produce reports based on a reference baseline and a profile.  Previously both 
-     the baseline and the profile had to describe complete products.  Any bundle that had resolver 
-     errors due to missing dependencies would be skipped.  Now these bundles will be processed.
-     </p>
-     <p>
-     Resolver errors can affect the results, therefore a list of resolver errors is included in the XML output
-     and warnings are added to the HTML report. To return to the old behavior of skipping
-     unresolved bundles, you can set <code>processunresolvedbundles="false"</code> on your Ant task.
-     </p>
-     <p>
-     <img src="images/unresolved-analysis.png" alt="Unresolved bundle in the analysis task"/>
-     </p>
-   </td>
-  </tr>
-  
-  <tr id="api-use-filters">
-    <td class="title">Problem filters apply to API Tools use scans</td>
-    <td class="content">
-      Problem filter files (.api_filter) can be used to filter problems reported by the API Tools analysis
-      task and the workspace analysis builder.  These filter files can now be applied to API Tools use scans.
-      Reference problems that are filtered out of the analysis results can also be filtered from the results
-      of use scans.
-      <p>
-      Filters are specified in the task using the same property as the analysis task.  Set the <em>filters</em>
-      attribute on the <em>apitooling.apiuse</em> task, specifying the root directory of API filter files.  Each
-      filter file must be in a folder with a filename matching the component name the filter file applies to.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="missing-filters-on-tasks">
-    <td class="title">API Tools tasks warn about missing include or exclude files</td>
-    <td class="content">
-      Many of the API Tools tasks, including Analysis, API Use, and API Freeze, provide <em>includelist</em> and
-      <em>excludelist</em> attributes which can be used to limit the reported problems. Previously,
-      if you set an include or exclude list, but the file wasn't found, the task would continue without warning
-      about the incorrect filtering.  Now a missing include or exclude list will result in the task failing with
-      an explanation.
-      <p>
-      <img src="images/missing-include.png" alt="Example console output for missing include"/>
-      </p>
-    </td>
-  </tr>
-  
-  <!-- ******************** Views and Editors ********************** -->
-  <tr>
-    <td id="ViewsAndEditors" class="section" colspan="2"><h2>Views and Editors</h2></td>
-  </tr>
-
-  <tr id="improved-feature-selection">
-    <td class="title">Improved feature selection dialog</td>
-    <td class="content">
-      The feature selection dialog used in wizards and editors has been enhanced with better wildcard support
-      and filtering options.
-      
-       <p><img src="images/featureselection.png" alt="Improved feature selection dialog"/></p> 
-    </td>
-  </tr>
-      
-  <tr id="additional-type-info">
-    <td class="title">Javadoc hover available in plug-in manifest editor</td>
-    <td class="content">
-      When editing the plugin.xml or manifest.mf files using the <b>Plug-in Manifest Editor</b>, 
-      opening content assist for type proposals will now display additional Javadoc information.
-      <p>
-        <img src="images/additional-type-info.png" alt="Additional info Javadoc hover for type proposals"/>
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="import-package">
-    <td class="title">New import package quick fixes</td>
-    <td class="content">
-      New quick fixes are available when you have an unresolved type in a Java file.  If the unresolved type
-      can be found in a package exported by a plug-in, a quick fix will be available to add an import
-      package entry to your plug-in manifest.  There is also a quick fix to add the exporting plug-in to
-      your manifest's require bundle header.
-      <p>
-      <img src="images/import-package.png" alt="Import package quick fix on an unresolved type"/>
-      </p>
-      <p>
-      If a package providing the type is available but the package is not exported by its plug-in, a quick fix will
-      offer to fix the providing plug-in's manifest. Only plug-ins in the workspace can be modified this
-      way.
-      </p>
-      <p>
-      <img src="images/export-package.png" alt="Export package quick fix on an unresolved type that is not exported"/>
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="bundles-in-category-editor">
-    <td class="title">Bundles in the category editor</td>
-    <td class="content">
-      The category editor now supports putting individual bundles into categories.
-      <p>      
-      The category editor creates a category.xml that can define categories that the contents of
-      a p2 repository should be organized into.  Previously only features could be specified as belonging
-      to a category and be visible to users.  Now individual bundles can be added to the category.xml.
-      </p>
-      <p>
-      <img src="images/category-editor.png" alt="Category editor can include individual bundles"/>
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="plugin-image-view">
-    <td class="title">Plug-in image browser view</td>
-    <td class="content">
-      A new view has been added to PDE.  The <b>Plug-in Image Browser</b> view displays icons and other
-      images from your target platform, running application or current workspace. 
-      <p>
-      	When an image is selected, additional information is displayed at the bottom of the view.  The
-        reference text can be used in plug-in extensions to refer to images in other bundles.
-      </p>
-      <p>
-        <img src="images/plugin-image-view.png" alt="The plug-in image browser view"/>
-      </p>
-    </td>
-  </tr>
-  
-  <!-- ******************** Misc ********************** -->
-  <tr>
-    <td id="Misc" class="section" colspan="2"><h2>Misc</h2></td>
-  </tr>
-
-  <tr id="default-launch-ee">
-    <td class="title">Launch configurations choose default execution environment</td>
-    <td class="content">
-      New PDE launch configurations (Eclipse Application, JUnit Plug-in Test, OSGi Framework) will
-      use a default execution environment to determine which Java runtime environment to launch with.
-      The launch configuration can be changed to use a different execution environment or a specific
-      JRE on the <b>Main</b> tab.
-      <p>
-        To find a valid execution environment, all known environments are checked against each bundle 
-        or plug-in that will be launched. Only an execution environment that is valid for all
-        plug-ins and bundles will be selected.  If no valid environment is found, a default JRE
-        will be chosen as before.
-      </p>
-      <p>
-        <img src="images/default-launch-ee.png" alt="Java runtime settings on the Main tab of PDE launch configurations"/>
-      </p>
-      <p>
-      	The JRE associated with the selected execution environment will be used to launch. To change 
-      	which JRE is associated with an execution environment, use the <b>Preferences > Java > Installed JREs > 
-      	Execution Environments</b> preference page.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="pde-5-bree">
-    <td class="title">PDE UI requires a 1.5 EE</td>
-    <td class="content">
-      The bundle required execution environment for the PDE UI bundles org.eclipse.pde.core and
-      org.eclipse.pde.ui is now J2SE-1.5.
-    </td>
-  </tr>
-  
-  <tr id="plugin-classpath-contributors">
-    <td class="title">New API to contribute to the classpath of plug-in projects</td>
-    <td class="content">
-      New API in PDE allows you to add additional classpath entries to a plug-in project.  Contribute a 
-      <em>Plug-in Classpath Contributor</em> via the <em>org.eclipse.pde.core.pluginClasspathContributors</em>
-      extension point.  Whenever the PDE classpath is computed or a new plug-in dependency is added, your classpath
-      contributor will be queried for additional entries.
-      <p>
-      If you are using Equinox Adapter hooks to load additional libraries at runtime you can use this API to add 
-      the correct libraries to the classpath at build time.
-      </p>
-      <p>
-      <img src="images/classpath-contributor.png" alt="An example classpath contributor extension"/>
-      </p>
-      </td>
-  </tr>
-  
-  <tr id="update-classpath-workspace">
-    <td class="title">Updating the classpath requires a workspace lock</td>
-    <td class="content">
-      When a change is made to a plug-in that forces a classpath update, an update job is created that
-      modifies the Plug-in Dependencies classpath container in the background. This job now acquires a workspace lock
-      to prevent other operations such as builders from running on a stale classpath.
-      <p>
-      This behaviour can be enabled in 4.2.2 by setting the system property <em>pde.lockWorkspaceForClasspath</em> to 
-      true.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="auto-start-all-plugins">
-    <td class="title">Default start level settings apply to all plug-ins</td>
-    <td class="content">
-      When editing the <b>Plug-ins</b> tab of an <b>Eclipse Application</b> launch configuration, the <b>Default
-      Start level</b> and <b>Default Auto-start</b> settings chosen at the top of the tab will be used when launching with
-      all workspace and enabled target plug-ins.  Previously this setting would only be used when launching a
-      specific list of plug-ins.
-      <p><img src="images/autostart-all-plugins.png" alt="All plug-ins selected on the tab"/></p>
-      <p><img src="images/autostart-levels.png" alt="Different default start level settings"/></p>
-    </td>
-  </tr>
-  
-  <tr id="pde-run-remembers-selection">
-    <td class="title">Running from PDE editors remembers previous launch</td>
-    <td class="content">
-      The PDE editors allow applications to be launched from the top toolbar of the <b>Manifest</b>, <b>Plug-in</b>
-      and <b>Product</b> editors.  By default PDE only provides one type of application to launch.  However, if you have additional tooling
-      installed such as RAP Tools, different application launches will be available in a drop down menu.
-      <p><img src="images/launch-order.png" alt="Ordering of launches in editor"/></p>
-      <p>
-      This menu now remembers which application was launched most recently and puts it at the top of the list.  The most
-      recent choice will be launched if the run button is pressed.  The order is saved between workbench
-      restarts.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="pde-junit-e4">
-    <td class="title">JUnit plug-in tests can run on Eclipse platform 4 workbench</td>
-    <td class="content">
-      Applications that use the Eclipse Platform 4 workbench API can now
-      use <b>JUnit Plug-in Test</b> launch configurations to test their plug-ins. Previously 
-      the tests would require the 3.x workbench API from the <code>org.eclipse.ui</code> bundle to 
-      hook into the workbench lifecycle.
-    </td>
-  </tr>
-  
-  <!-- ****************** END OF N&N TABLE ****************** -->
-  </tbody>
-</table>
-
-<p align="center"><a href="eclipse-news-part3.html">Previous</a>&nbsp;&nbsp;&nbsp;&nbsp; <font color="#808080">Next</font></p>
-
-</body>
-</html>
diff --git a/platform/4.3/final/eclipse-news.html b/platform/4.3/final/eclipse-news.html
deleted file mode 100644
index 94fd04e..0000000
--- a/platform/4.3/final/eclipse-news.html
+++ /dev/null
@@ -1,35 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2012. This page is made available under license. For full details see: http://www.eclipse.org/legal/notice.html" >
-<meta http-equiv="Content-Language" content="en-us">
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<link rel="stylesheet" href="default_style.css" charset="ISO-8859-1" type="text/css">
-<title>Eclipse Kepler - New and Noteworthy</title>
-</head>
-<body>
-
-<h1>Eclipse Kepler - New and Noteworthy</h1>
-
-<div align="right"><i>
-I demonstrate by means of philosophy that the earth is round, <br>
-and is inhabited on all sides; that it is insignificantly small, <br>
-and is borne through the stars.</i> <strong>Johannes Kepler</strong>, Astronomia Nova
-</div>
-
-<p>Welcome to Kepler, the simultaneous Eclipse release for 2013, including
-content from seventy two Eclipse projects. The Eclipse platform and related resources
-can be downloaded from the <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">Eclipse Project downloads page</a>.
-Here are some of the more noteworthy things available in the thirteenth annual release of the Eclipse project SDK.</p>
-
-<blockquote>
-  <ul>
-    <li><a href="eclipse-news-part1.html">New features in the Platform and Equinox</a></li>
-    <li><a href="eclipse-news-part2.html">New features for Java developers</a></li>
-    <li><a href="eclipse-news-part3.html">New APIs in the Platform and Equinox</a></li>
-    <li><a href="eclipse-news-part4.html">New features for plug-in developers</a></li>
-  </ul>
-</blockquote>
-
-</body>
-</html>
diff --git a/platform/4.3/final/images/additional-info.png b/platform/4.3/final/images/additional-info.png
deleted file mode 100644
index c8b741b..0000000
--- a/platform/4.3/final/images/additional-info.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/additional-type-info.png b/platform/4.3/final/images/additional-type-info.png
deleted file mode 100644
index 3f24504..0000000
--- a/platform/4.3/final/images/additional-type-info.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/api-parent-not-visible.png b/platform/4.3/final/images/api-parent-not-visible.png
deleted file mode 100644
index 1003977..0000000
--- a/platform/4.3/final/images/api-parent-not-visible.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/autostart-all-plugins.png b/platform/4.3/final/images/autostart-all-plugins.png
deleted file mode 100644
index 3858413..0000000
--- a/platform/4.3/final/images/autostart-all-plugins.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/autostart-levels.png b/platform/4.3/final/images/autostart-levels.png
deleted file mode 100644
index 4f00f01..0000000
--- a/platform/4.3/final/images/autostart-levels.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/bidi.png b/platform/4.3/final/images/bidi.png
deleted file mode 100644
index 4aa20af..0000000
--- a/platform/4.3/final/images/bidi.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/category-editor.png b/platform/4.3/final/images/category-editor.png
deleted file mode 100644
index 9c49163..0000000
--- a/platform/4.3/final/images/category-editor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/classpath-contributor.png b/platform/4.3/final/images/classpath-contributor.png
deleted file mode 100644
index 67e2913..0000000
--- a/platform/4.3/final/images/classpath-contributor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/close-quietly-example.png b/platform/4.3/final/images/close-quietly-example.png
deleted file mode 100644
index 6c29f05..0000000
--- a/platform/4.3/final/images/close-quietly-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/combine-strings.png b/platform/4.3/final/images/combine-strings.png
deleted file mode 100644
index 7765407..0000000
--- a/platform/4.3/final/images/combine-strings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/content-assist.png b/platform/4.3/final/images/content-assist.png
deleted file mode 100644
index a3b003c..0000000
--- a/platform/4.3/final/images/content-assist.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/convert-if-else-to-switch.png b/platform/4.3/final/images/convert-if-else-to-switch.png
deleted file mode 100644
index be3ea31..0000000
--- a/platform/4.3/final/images/convert-if-else-to-switch.png
+++ /dev/null
Binary files differ
diff --git "a/platform/4.3/final/images/convert-to-if-\041-return.png" "b/platform/4.3/final/images/convert-to-if-\041-return.png"
deleted file mode 100644
index 5cd0b93..0000000
--- "a/platform/4.3/final/images/convert-to-if-\041-return.png"
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/create-loop-variable.png b/platform/4.3/final/images/create-loop-variable.png
deleted file mode 100644
index c23d4de..0000000
--- a/platform/4.3/final/images/create-loop-variable.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/declaration-view-indicating-outofsync.png b/platform/4.3/final/images/declaration-view-indicating-outofsync.png
deleted file mode 100644
index 4e5e98d..0000000
--- a/platform/4.3/final/images/declaration-view-indicating-outofsync.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/default-launch-ee.png b/platform/4.3/final/images/default-launch-ee.png
deleted file mode 100644
index bd17db6..0000000
--- a/platform/4.3/final/images/default-launch-ee.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/detached-sash.png b/platform/4.3/final/images/detached-sash.png
deleted file mode 100644
index d904dee..0000000
--- a/platform/4.3/final/images/detached-sash.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/dom-structure.png b/platform/4.3/final/images/dom-structure.png
deleted file mode 100644
index dc19e15..0000000
--- a/platform/4.3/final/images/dom-structure.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/eedescfeature.png b/platform/4.3/final/images/eedescfeature.png
deleted file mode 100644
index fe8e9f1..0000000
--- a/platform/4.3/final/images/eedescfeature.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/export-package.png b/platform/4.3/final/images/export-package.png
deleted file mode 100644
index ec50bb7..0000000
--- a/platform/4.3/final/images/export-package.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/featureselection.png b/platform/4.3/final/images/featureselection.png
deleted file mode 100644
index cf9dc8c..0000000
--- a/platform/4.3/final/images/featureselection.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/gtk3.png b/platform/4.3/final/images/gtk3.png
deleted file mode 100644
index a9468b4..0000000
--- a/platform/4.3/final/images/gtk3.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/illegal-ambiguous-varargs-error-Juno.png b/platform/4.3/final/images/illegal-ambiguous-varargs-error-Juno.png
deleted file mode 100644
index 5d4aac9..0000000
--- a/platform/4.3/final/images/illegal-ambiguous-varargs-error-Juno.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/illegal-ambiguous-varargs-error.png b/platform/4.3/final/images/illegal-ambiguous-varargs-error.png
deleted file mode 100644
index 22290a0..0000000
--- a/platform/4.3/final/images/illegal-ambiguous-varargs-error.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/illegal-ambiguous-varargs-error.txt b/platform/4.3/final/images/illegal-ambiguous-varargs-error.txt
deleted file mode 100644
index 9630ec5..0000000
--- a/platform/4.3/final/images/illegal-ambiguous-varargs-error.txt
+++ /dev/null
@@ -1,11 +0,0 @@
-    public static void test(int... a) {
-        System.out.println(Arrays.toString(a));
-    }
-    
-    public static void test(Object... a) {
-        System.out.println(Arrays.toString(a));
-    }
-    
-    public static void main(String[] args) {
-        test(1); // 'test' flagged ambiguous
-    }
diff --git a/platform/4.3/final/images/illegal-ambiguous-varargs-error2.png b/platform/4.3/final/images/illegal-ambiguous-varargs-error2.png
deleted file mode 100644
index 27f715e..0000000
--- a/platform/4.3/final/images/illegal-ambiguous-varargs-error2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/illegal-ambiguous-varargs-error2.txt b/platform/4.3/final/images/illegal-ambiguous-varargs-error2.txt
deleted file mode 100644
index 4a990bd..0000000
--- a/platform/4.3/final/images/illegal-ambiguous-varargs-error2.txt
+++ /dev/null
@@ -1,6 +0,0 @@
-    public static void foo(int... i) { }
-    public static void foo(double... d) { }
-    
-    public static void main(String[] args) {
-        foo(1, 2, 3); // foo flagged ambiguous
-    }
diff --git a/platform/4.3/final/images/import-nested.png b/platform/4.3/final/images/import-nested.png
deleted file mode 100644
index 271a2ad..0000000
--- a/platform/4.3/final/images/import-nested.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/import-package.png b/platform/4.3/final/images/import-package.png
deleted file mode 100644
index 7d13527..0000000
--- a/platform/4.3/final/images/import-package.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/inherit-null-annotations-example.png b/platform/4.3/final/images/inherit-null-annotations-example.png
deleted file mode 100644
index a51a9da..0000000
--- a/platform/4.3/final/images/inherit-null-annotations-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/inherit-null-annotations-example2.png b/platform/4.3/final/images/inherit-null-annotations-example2.png
deleted file mode 100644
index 5f41dd9..0000000
--- a/platform/4.3/final/images/inherit-null-annotations-example2.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/inherit-null-annotations-option.png b/platform/4.3/final/images/inherit-null-annotations-option.png
deleted file mode 100644
index 322f055..0000000
--- a/platform/4.3/final/images/inherit-null-annotations-option.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/javadoc-package-names-linked.png b/platform/4.3/final/images/javadoc-package-names-linked.png
deleted file mode 100644
index 52d6137..0000000
--- a/platform/4.3/final/images/javadoc-package-names-linked.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/javadoc-view-target.png b/platform/4.3/final/images/javadoc-view-target.png
deleted file mode 100644
index 25305da..0000000
--- a/platform/4.3/final/images/javadoc-view-target.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/junit-templates.png b/platform/4.3/final/images/junit-templates.png
deleted file mode 100644
index 00a9a62..0000000
--- a/platform/4.3/final/images/junit-templates.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/junit-view-assumptions.png b/platform/4.3/final/images/junit-view-assumptions.png
deleted file mode 100644
index 4f29f91..0000000
--- a/platform/4.3/final/images/junit-view-assumptions.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/launch-order.png b/platform/4.3/final/images/launch-order.png
deleted file mode 100644
index d85ca91..0000000
--- a/platform/4.3/final/images/launch-order.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/lcd-warnings.png b/platform/4.3/final/images/lcd-warnings.png
deleted file mode 100644
index 2ade3b5..0000000
--- a/platform/4.3/final/images/lcd-warnings.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/linkColor.png b/platform/4.3/final/images/linkColor.png
deleted file mode 100644
index c6f4381..0000000
--- a/platform/4.3/final/images/linkColor.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/migration-wizard.png b/platform/4.3/final/images/migration-wizard.png
deleted file mode 100644
index d19bee9..0000000
--- a/platform/4.3/final/images/migration-wizard.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/missing-include.png b/platform/4.3/final/images/missing-include.png
deleted file mode 100644
index 304a810..0000000
--- a/platform/4.3/final/images/missing-include.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/no-reference.png b/platform/4.3/final/images/no-reference.png
deleted file mode 100644
index 45d52bc..0000000
--- a/platform/4.3/final/images/no-reference.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/null-annotations-for-fields-examples.png b/platform/4.3/final/images/null-annotations-for-fields-examples.png
deleted file mode 100644
index 4276694..0000000
--- a/platform/4.3/final/images/null-annotations-for-fields-examples.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/null-annotations-for-fields-examples.txt b/platform/4.3/final/images/null-annotations-for-fields-examples.txt
deleted file mode 100644
index 648bc94..0000000
--- a/platform/4.3/final/images/null-annotations-for-fields-examples.txt
+++ /dev/null
@@ -1,26 +0,0 @@
-import org.eclipse.jdt.annotation.NonNull;
-import org.eclipse.jdt.annotation.Nullable;
-
-public class NullAnnotatedFields {
-    @NonNull Letter nonNull;
-    @Nullable Letter nullable;
-    String test() {
-        nonNull.print();
-        nullable.print();
-        nonNull = null;
-
-        if (nullable != null)
-            nullable.print(); // protected
-
-        nullable = new Letter();
-        bar();     // spoils protection
-        return nullable.toString();
-    }
-    void bar() {
-       
-    }
-}
-// --- not shown in the screenshot: --- 
-class Letter {
-    void print() {}
-}
\ No newline at end of file
diff --git a/platform/4.3/final/images/only-include-exported.png b/platform/4.3/final/images/only-include-exported.png
deleted file mode 100644
index e6cacc2..0000000
--- a/platform/4.3/final/images/only-include-exported.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/open-resource-buttons.png b/platform/4.3/final/images/open-resource-buttons.png
deleted file mode 100644
index a741513..0000000
--- a/platform/4.3/final/images/open-resource-buttons.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/option-syntactic-null-analysis-for-fields.png b/platform/4.3/final/images/option-syntactic-null-analysis-for-fields.png
deleted file mode 100644
index fbe2422..0000000
--- a/platform/4.3/final/images/option-syntactic-null-analysis-for-fields.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/override-annotation-code-style.png b/platform/4.3/final/images/override-annotation-code-style.png
deleted file mode 100644
index 6da2b0a..0000000
--- a/platform/4.3/final/images/override-annotation-code-style.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/override-annotation-compiler.png b/platform/4.3/final/images/override-annotation-compiler.png
deleted file mode 100644
index 3b0516c..0000000
--- a/platform/4.3/final/images/override-annotation-compiler.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/package-javadoc-hover-examples.png b/platform/4.3/final/images/package-javadoc-hover-examples.png
deleted file mode 100644
index 8a580c9..0000000
--- a/platform/4.3/final/images/package-javadoc-hover-examples.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/plugin-image-view.png b/platform/4.3/final/images/plugin-image-view.png
deleted file mode 100644
index bf7815d..0000000
--- a/platform/4.3/final/images/plugin-image-view.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/pre-fill-package-name.png b/platform/4.3/final/images/pre-fill-package-name.png
deleted file mode 100644
index 230704e..0000000
--- a/platform/4.3/final/images/pre-fill-package-name.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/quickassist-for-unused-type-parameter-example.png b/platform/4.3/final/images/quickassist-for-unused-type-parameter-example.png
deleted file mode 100644
index 5c63e66..0000000
--- a/platform/4.3/final/images/quickassist-for-unused-type-parameter-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/remediation.png b/platform/4.3/final/images/remediation.png
deleted file mode 100644
index 72101c3..0000000
--- a/platform/4.3/final/images/remediation.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/speed.jpg b/platform/4.3/final/images/speed.jpg
deleted file mode 100644
index f42c47e..0000000
--- a/platform/4.3/final/images/speed.jpg
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/trim-drag.png b/platform/4.3/final/images/trim-drag.png
deleted file mode 100644
index 9c79b41..0000000
--- a/platform/4.3/final/images/trim-drag.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/unresolved-analysis.png b/platform/4.3/final/images/unresolved-analysis.png
deleted file mode 100644
index b92b1a6..0000000
--- a/platform/4.3/final/images/unresolved-analysis.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/unused-type-parameter.png b/platform/4.3/final/images/unused-type-parameter.png
deleted file mode 100644
index 0e6df20..0000000
--- a/platform/4.3/final/images/unused-type-parameter.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/use-last-page-option.png b/platform/4.3/final/images/use-last-page-option.png
deleted file mode 100644
index 806f02e..0000000
--- a/platform/4.3/final/images/use-last-page-option.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/use-scan.png b/platform/4.3/final/images/use-scan.png
deleted file mode 100644
index f91028e..0000000
--- a/platform/4.3/final/images/use-scan.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/using-no-reference.png b/platform/4.3/final/images/using-no-reference.png
deleted file mode 100644
index 51518c8..0000000
--- a/platform/4.3/final/images/using-no-reference.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/vertical-switcher.png b/platform/4.3/final/images/vertical-switcher.png
deleted file mode 100644
index 8798efa..0000000
--- a/platform/4.3/final/images/vertical-switcher.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/whole-word-option.png b/platform/4.3/final/images/whole-word-option.png
deleted file mode 100644
index ec15556..0000000
--- a/platform/4.3/final/images/whole-word-option.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/final/images/x-start-on-first-thread.png b/platform/4.3/final/images/x-start-on-first-thread.png
deleted file mode 100644
index 76ecce0..0000000
--- a/platform/4.3/final/images/x-start-on-first-thread.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.3/whats-new-template/eclipse-whats-new-template.html b/platform/4.3/whats-new-template/eclipse-whats-new-template.html
deleted file mode 100644
index 51a3c61..0000000
--- a/platform/4.3/whats-new-template/eclipse-whats-new-template.html
+++ /dev/null
@@ -1,194 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" 
-        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-  <style type="text/css">
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt;}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt;}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px;}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt;}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px;}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold;}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt;}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold;}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm;}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold;}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF;}
-a.bar:link {  text-decoration: none; color: #FFFFFF;}
-a.bar:visited {  color: #FFFFFF; text-decoration: none;}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline;}
-a.bar {  color: #FFFFFF;}
-
-.section {font-size: 20px; font-weight: bold;}
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
-  </style>
-<title>Eclipse &quot;New and Noteworthy&quot; Template</title>
-</head>
-
-<body>
-<h1>Eclipse &quot;New and Noteworthy&quot; Template</h1>
-<p>Last revised 2012-11-02.</p>
-<p>This is the template for the &quot;New and Noteworthy&quot; document that
-  accompanies each Eclipse project milestone build.</p>
-<p>Note: This template document is XHTML 1.0 Transitional. Please use the W3C <a href="http://validator.w3.org/#validate_by_input">XHTML
-    Markup Validation Service</a> to check your document's markup before submitting.
-    This will detect screwed up HTML tags, images without an &quot;alt&quot;
-    attribute, and other tedious little details.</p>
-
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-  <li><a href="#Equinox">Equinox</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%" summary="news entries">
-
-  <tr>
-    <td id="Instructions" class="section" colspan="2">
-      <h2>Instructions</h2>
-    </td>
-  </tr>
-  
-  <tr id="item-name">
-    <td class="title">Item title, in sentence style, no trailing
-        punctuation, with unique id attribute on &lt;tr&gt;</td>
-    <td class="content">
-        A blurb pitched to the Eclipse community
-        (not just to members of the Eclipse Platform development team). Tell
-        end users about changes they'll see in the UI. Tell component writers
-        about changes they'll see at the client- and server-side APIs. Try to
-        generate some excitement; save the boring details for the manual; be short and don't repeat yourself. The
-        description should be complete sentences, with trailing punctuation.
-      <p>Use active voice (say "you", not "the user"), and follow other advice in the
-        <a href="http://wiki.eclipse.org/Eclipse_Doc_Style_Guide#topic-content">Topic&nbsp;Content</a>
-        section of the Eclipse Doc Style Guidelines.
-      </p>
-      <p>Stick to the default font and size. Make command names (<b>Quick Fix</b>),
-        keyboard shortcuts (<b>Ctrl+1</b>), and preference page paths
-        (<b>Preferences &gt; General &gt; Keys</b>) bold.
-      </p>
-      <p>Do <em>not</em> enclose the first paragraph of an item in <code>&lt;p&gt;&lt;/p&gt;</code> tags.
-      </p>
-    </td>
-  </tr>
-  
-  <tr id="screenshots">
-    <td class="title">Screenshots</td>
-    <td class="content">
-        If a small image sheds light, place it below the description, in a separate
-        paragraph. Regular screen snapshots should be done on Windows 7. Crop
-        out any extraneous stuff to focus the reader's attention on your new
-        feature. The image should be
-        <b>no more than 519 pixels wide</b> and in <b>PNG</b> format (as opposed
-        to GIF, TIF, BMP, or JPG). Use PNG-8 if your image doesn't have a lot of color,
-        or PNG-24 if the screen shot uses enough color to warrant additional color depth.
-        See also the 
-        <a href="http://wiki.eclipse.org/Eclipse_Doc_Style_Guide#graphics">Graphics</a>
-        section of the Eclipse Doc Style Guidelines.
-      <p>The Windows <b>Snipping Tool</b> actually saves to PNG on Windows 7 and can easily be
-        used to crop and save screenshots:</p>
-      <ul>
-        <li>Arrange the windows for the shot</li>
-        <li>Use the Windows <b>Snipping Tool</b> to capture part of the screen</li>
-        <li>Use <b>File &gt; Save As</b> to save the screenshot as a PNG</li>
-        <li>Overlays such as red circles or boxes to call out details can be done using Microsoft Paint</li>
-      </ul>
-      <p>Name the file is a way that is appropriate and specific to the item
-        (e.g., key-bindings.png, rather than something generic like image.png).
-        Use all <b>lowercase</b> letters in the image file name, including the &quot;<b>.png</b>&quot; 
-        file extension. As a separator, use <b>hyphen</b> &quot;-&quot; rather than
-        underscore 
-        &quot;_&quot;. </p>
-      <p>Put all the images in a sibling directory named &quot;images&quot;.
-        This gives XHTML like:<br/>
-        <code>&lt;img src=&quot;images/foo-view.png&quot; alt=&quot;&quot;/&gt;</code><br/>
-        Include a suitable <a href="http://www.w3.org/TR/html4/struct/objects.html#h-13.8"><code>alt</code></a> attribute.
-        The alt text should be empty ("") if the image just illustrates the text.
-        Only use the alt text to add information that is not accessible if the page is rendered without images.
-        Don't write <code>alt="Screenshot of <i>the XY dialog</i>"</code>. Blind users shouldn't have to skip useless repetitions.</p>
-      <p>If the <code>alt</code> attribute text cannot sufficiently replace the image contents
-        (e.g. for a screenshot that shows source code), then enclose the img element in a link
-        to a plain &quot;.txt&quot; file with the same name as the image:<br/>
-        <code>&lt;a href=&quot;images/foo-view.txt&quot;&gt;&lt;img ...</code></p>
-      <p>The images should be left-justified (as opposed to centered). Do not embed the width and height of the image.</p>
-      <p>Use the W3C <a href="http://validator.w3.org/#validate_by_input">XHTML
-          Markup Validation Service</a> to check your document's markup before
-          submitting.</p></td>
-  </tr>
-  
-  <tr>
-    <td id="Platform" class="section" colspan="2">
-      <h2>Platform</h2>
-    </td>
-  </tr>
-  
-  <tr id="first-item">
-    <td class="title">First item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-  
-  <tr id="second-item">
-    <td class="title">Second item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-
-
-  <tr>
-    <td id="JDT" class="section" colspan="2">
-      <h2>JDT</h2>
-    </td>
-  </tr>
-  
-  <tr id="first-jdt-item">
-    <td class="title">First item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-
-
-  <tr>
-    <td id="PDE" class="section" colspan="2">
-      <h2>PDE</h2>
-    </td>
-  </tr>
-  
-  <tr id="first-pde-item">
-    <td class="title">First item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-
-
-  <tr>
-    <td id="Equinox" class="section" colspan="2">
-      <h2>Equinox</h2>
-    </td>
-  </tr>
-  
-  <tr id="first-equinox-item">
-    <td class="title">First item</td>
-    <td class="content">
-      Item blurb.
-    </td>
-  </tr>
-
-
-  <tr>
-    <td colspan="2"></td>
-  </tr>
-  
-</table>
-</body>
-</html>
diff --git a/platform/4.4/M1/default_style.css b/platform/4.4/M1/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.4/M1/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.4/M1/eclipse-news-M1.html b/platform/4.4/M1/eclipse-news-M1.html
deleted file mode 100644
index 3f73494..0000000
--- a/platform/4.4/M1/eclipse-news-M1.html
+++ /dev/null
@@ -1,263 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Project 4.4 M1 News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.4 M1 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M1
-  (August 9, 2013) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#PDE">PDE</a></li>
-  <li><a href="#Equinox">Equinox</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  <tr id="e4-views-1">
-    <td class="title">Contribute E4 Views into the IDE</td>
-    <td class="content">
-      As part of our goal to remove some of the barriers between e4-based code and the IDE
-      we've just added a new element 'e4view' into the <code>org.eclipse.ui.views</code>
-      extension point. This allows you to declare a new view for the IDE whose implementation
-      is done in the e4 style (i.e. an annotated POJO).
-      <p>
-        <img src="images/new-e4view-extension.png" alt="new extension"/>
-      </p><p>
-        The new type of extension is identical to the original 'view' except for relaxing the
-        requirement that the 'class' implement IViewPart.
-      </p><p>
-        This is the first trial run for this type of extension. Once we are sure we have the pattern
-        correct, we'll make similar changes to other extension points such as <code>org.eclipse.ui.menus</code>.
-      </p><p>
-        For those that are unaware of the e4 way of coding, here's what the implementation of an e4 view
-        looks like:
-      </p>
-      <pre>
-import javax.annotation.PostConstruct;
-import org.eclipse.e4.ui.di.Focus;
-import org.eclipse.swt.SWT;
-import org.eclipse.swt.widgets.Composite;
-import org.eclipse.swt.widgets.Label;
-
-public class RealE4View {
-	Label label;
-
-	@PostConstruct
-	void createView(Composite parent) {
-		label = new Label(parent, SWT.BORDER);	
-		label.setText("Testing");
-	}
-
-	@Focus
-	void setFocus() {
-		label.setFocus();
-	}
-}
-      </pre>
-      <p>
-        Note how it's a simple POJO and how few dependencies it has; this has already proven itself as
-        a far more convenient way to write the code and has great advantages in testing (because of its
-        few dependencies).
-      </p>
-    </td>
-  </tr>
-  <tr id="e4-views-2">
-    <td class="title">Tweaking the UX</td>
-    <td class="content">
-      We've finally gotten to the point where we can return and address some of the current pain
-      points you all see when using Eclipse 4. This will be part of our focus for each milestone
-      in Luna...while not necessarily 'New' these changes *are* 'Noteworthy'...;-).
-      <p>
-        First up is fixing how we handle minimized views that are brought up by the framework
-        being hard to dismiss. The most common (and justifiably complained about) use case for
-        this is having the Debug view overlay the editor when it hits a breakpoint. This has
-        been refactored to match the 3.x behavior more closely and should now work as expected.
-      </p><p>
-        Next up will be re-enabling the ability to reorder the perspectives on the perspective bar.
-      </p>
-    </td>
-  </tr>
-  <tr id="signed-executables">
-    <td class="title">Signed SDK Executables (for Windows and Mac)</td>
-    <td class="content">Thanks to the efforts of the
-              Eclipse Foundation (see <a
-              href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=388878">bug
-                388878</a>), we now provide signed Windows and Mac
-              executables for the Eclipse SDK. This improves the initial impression of the
-              software, as well as improves security for you, since
-              there is no need to disable "Gatekeeper" or other
-              security measures of the operating systems.
-    </td>
-  </tr>
-
-  <tr id="recenter-command">
-    <td class="title">Improved Recenter command</td>
-    <td class="content">
-        Like in Emacs, the <b>Recenter</b> command in textual editors now cycles between center, bottom and top.
-    </td>
-  </tr>
-
-  <tr id="ant-1.9.2-update">
-    <td class="title">Ant 1.9.2</td>
-
-    <td class="content">
-    	The platform has been updated to use the latest version of Apache Ant (1.9.2). For
-    more information on what is new in Ant 1.9.2, see the official <a href="http://mirror.olnevhost.net/pub/apache//ant/README.html">what's new</a>.
-    </td>
-  </tr>
-  <tr id="ant-bree-update">
-    <td class="title">Platform Ant BREE update</td>
-
-    <td class="content">
-    	Platform Ant has had a BREE update to require a Java 1.6 compatible execution environment (or newer).
-    </td>
-  </tr>
-  <tr id="ant-view-collapse-all">
-    <td class="title">Collapse All in Ant view</td>
-
-    <td class="content">
-    	The Ant view now supports the <b>Collapse All</b> command:
-    	<p>
-    	<img src="images/ant-view.png" alt="The Ant view showing the collapse all action"/>
-    	</p>
-    </td>
-  </tr>
-  <tr>
-    <td class="title">Platform Debug BREE update</td>
-
-    <td class="content">
-    	Platform Debug has had a BREE update to require a Java 1.6 compatible execution environment (or newer).
-    </td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr id="junit-failure-trace-font">
-    <td class="title">Failure trace font for the JUnit view</td>
-    <td class="content">
-     The font for the failure trace in the JUnit view is now configurable on the <b>General &gt; Appearance &gt; Colors and Fonts</b> preference page.
-     <p><img src="images/junit-failure-trace-font.png" alt=""/></p>
-    </td>
-  </tr>
-  <tr id="contrib-jres">
-    <td class="title">Contributed VMs are more recognizable</td>
-
-    <td class="content">
-    	You can't remove VMs that have been contributed to Eclipse via the <code>org.eclipse.jdt.launching.vmInstalls</code> extension point.This
-    	fact is now more recognizable:
-    	<p>
-    	<img src="images/contrib-vm.png" alt="The Installed JREs preference page showing a contributed VM install"/>
-    	</p>
-    </td>
-  </tr>
-  <tr id="improved-hcr">
-  	<td class="title">Improved HCR for member types</td>
-  	
-  	<td class="content">
-  		Hot Code Replace (HCR) has been improved in the Java debugger to ensure the correct method is dropped to
-  		in member types (inner / anonymous / local classes).
-  		<p>
-  		For more information see the <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=409023">bugzilla entry</a>.
-  		</p>
-  	</td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  <tr id="target-statusbar">
-    <td class="title">Display target platform in the status bar</td>
-    <td class="content">
-     You can now have target platform information displayed in the workbench status bar.  Currently it displays the active target
-     name and double clicking on it will open the <b>Target Platform</b> preference page. This feature can be enabled on the
-     <b>General &gt; Plug-in Development</b> preference page.
-     <p><img src="images/target-statusbar.png" alt="Target platform in the status bar"/></p>
-    </td>
-  </tr>
-  <tr id="pde-tracing">
-    <td class="title">PDE UI tracing options available</td>
-    <td class="content">
-     The tracing options provided by PDE UI can now be enabled from the <b>General &gt; Tracing</b> preference page:
-     <p><img src="images/pde-tracing.png" alt="PDE tracing options"/></p>
-    </td>
-  </tr>
-  <tr id="warn-platformadmin-unavailable">
-    <td class="title">Warning if PlatformAdmin is unavailable</td>
-    <td class="content">
-     PDE requires the PlatformAdmin service to function. The Equinox Framework has moved this service to the <b>org.eclipse.osgi.compatibility.state</b>
-     compatibility fragment.  If the fragment is not installed, PDE will write an error to the log and will not function correctly. The fragment
-     is included in the Eclipse SDK, so most users will be unaffected.
-     <p><img src="images/platformadmin-message.png" alt="Error message for PlatformAdmin unavailable"/></p>
-    </td>
-  </tr>
-    <tr id="pde-build-6">
-    <td class="title">PDE Build moved to JavaSE-1.6</td>
-    <td class="content">
-     The org.eclipse.pde.build bundle now has a bundle required execution environment (BREE) of JavaSE-1.6, matching the Platform Ant bundles.
-    </td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="Equinox">Equinox</td>
-  </tr>
-  <tr id="framework-update">
-    <td class="title">Equinox OSGi framework update</td>
-
-    <td class="content">
-      The Equinox Framework implementation has been updated to implement the latest
-      API available for the upcoming OSGi R6 Framework specification.  The OSGi
-      R6 Core Framework specification (finalized in March 2014) will contain
-      enhancements in the following areas:
-      <ul>
-         <li> Introduction of Service Scopes to the OSGi Service Registry
-             (<a href="http://www.osgi.org/Specifications/Drafts">RFC 195</a>)
-         </li>
-         <li> Improvements of Weaving Hooks
-             (<a href="http://www.osgi.org/Specifications/Drafts">RFC 191</a>)
-         </li>
-         <li> Clarification of hooks on the system bundle
-             (<a href="http://www.osgi.org/Specifications/Drafts">RFC 198</a>)
-         </li>
-         <li> Native environment namespace
-             (<a href="http://www.osgi.org/Specifications/Drafts">RFC 188</a>)
-         </li>
-         <li> Data Transfer Objects
-             (<a href="http://www.osgi.org/Specifications/Drafts">RFC 185</a>)
-         </li>
-         <li> Addition of FrameworkWiring.findProviders
-         </li>
-      </ul>
-      From an Equinox perspective these are considered incremental enhancements.
-      The enhancements mentioned above are implemented in M1.  A majority of the
-      development effort during this release cycle is focused on refactoring and, in
-      many cases, rewriting the core Equinox Framework implementation to be based on
-      the OSGi generic dependency model.
-      <p>
-      For most consumers and developers this change should not be noticed.  But, as
-      documented in the <a href="http://wiki.eclipse.org/Equinox/Luna_Framework">wiki</a>,
-      there are four main areas of concern that the community should be aware of:
-      </p>
-      <ul>
-         <li>The Framework no longer uses the old Equinox resolver API
-             org.eclipse.osgi.service.resolver internally to resolve bundles.</li>
-         <li>All Equinox Framework specific hook implementations are broken and will
-             need to migrate.</li>
-         <li>Removal of old style plug-in support. A compatibility fragment is available to add the support back.</li>
-         <li>Removal of PlatformAdmin Service Implementation. A compatibility fragment is available to add support back.</li>
-      </ul>
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2">  </td>
-  </tr>
-</table>
-</body>
-</html>
diff --git a/platform/4.4/M1/images/ant-view.png b/platform/4.4/M1/images/ant-view.png
deleted file mode 100644
index e0cecc4..0000000
--- a/platform/4.4/M1/images/ant-view.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M1/images/contrib-vm.png b/platform/4.4/M1/images/contrib-vm.png
deleted file mode 100644
index d44d630..0000000
--- a/platform/4.4/M1/images/contrib-vm.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M1/images/junit-failure-trace-font.png b/platform/4.4/M1/images/junit-failure-trace-font.png
deleted file mode 100644
index 6041bd9..0000000
--- a/platform/4.4/M1/images/junit-failure-trace-font.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M1/images/new-e4view-extension.png b/platform/4.4/M1/images/new-e4view-extension.png
deleted file mode 100644
index 63a67e5..0000000
--- a/platform/4.4/M1/images/new-e4view-extension.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M1/images/pde-tracing.png b/platform/4.4/M1/images/pde-tracing.png
deleted file mode 100644
index d7fe1a3..0000000
--- a/platform/4.4/M1/images/pde-tracing.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M1/images/platformadmin-message.png b/platform/4.4/M1/images/platformadmin-message.png
deleted file mode 100644
index bbb3227..0000000
--- a/platform/4.4/M1/images/platformadmin-message.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M1/images/target-statusbar.png b/platform/4.4/M1/images/target-statusbar.png
deleted file mode 100644
index 9dcf35b..0000000
--- a/platform/4.4/M1/images/target-statusbar.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M2/default_style.css b/platform/4.4/M2/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.4/M2/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.4/M2/eclipse-news-M2.html b/platform/4.4/M2/eclipse-news-M2.html
deleted file mode 100644
index 2eabee0..0000000
--- a/platform/4.4/M2/eclipse-news-M2.html
+++ /dev/null
@@ -1,179 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Project 4.4 M2 News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.4 M2 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M2 
-  (September 20, 2013) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#PDE">PDE</a></li>
-  <li><a href="#Equinox">Equinox</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-  <tr id="reorder-perspectives"> 
-    <td class="title">Perspective re-ordering</td>
-    <td class="content">
-      You can now drag and drop the items in the perspective switcher to change the order of your open perspectives.
-    <p><img src="images/move-persp-items.png" alt="moveitems"/></p>
-    </td>
-  </tr>
-  <tr id="timing-api"> 
-    <td class="title">Added UI timing API</td>
-    <td class="content"> 
-      SWT has added two new events, <tt>SWT.PreEvent</tt> and <tt>SWT.PostEvent</tt>,
-      which are sent before and after all events and async runnables. These events can
-      be used to measure the time spent on processing any events. This 
-      can be useful for detecting slow event listeners. Because of its pervasive effect
-      on all events, this listener should be used with <b>extreme</b> caution.
-      For an example of how this can be used, take a look at the 
-      <a href="http://git.eclipse.org/c/platform/eclipse.platform.swt.git/tree/examples/org.eclipse.swt.examples.watchdog">
-      Watchdog</a> plugin in SWT examples.
-    </td>
-  </tr>
-  <tr id="debug-examples"> 
-    <td class="title">New debugger examples</td>
-    <td class="content"> 
-      New examples have been added to the Platform Debug git repository. The <code>org.eclipse.debug.examples.mixedmode</code> project demonstrates
-      how to use Debug's mixed-mode launching support. The <code>org.eclipse.debug.examples.memory</code> project provides sample content to display
-      in the <b>Memory</b> and <b>Registers</b> views.
-    </td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-  <tr id="api-tag-visibility">
-    <td class="title">API Tools javadoc tag visibility matches Java Language Specification</td>
-    <td class="content">
-     API Tools supports API restrictions using <a href="http://wiki.eclipse.org/PDE/API_Tools/Javadoc_Tags">javadoc tags</a> such as 
-     @noextend and @noreference. The API Tools builder has an option to add problem markers for invalid use of the tags. The
-     logic to check whether a tag is valid has been upgraded and now follows the visibility rules in the 
-     <a href="http://docs.oracle.com/javase/specs/">Java Language Specification (JLS)</a>.
-     <p><img src="images/tag-visibility.png" alt="Example tag visibility problem"/></p>
-    </td>
-  </tr>
-  <tr id="api-tools-bree">
-    <td class="title">API Tools moved to JavaSE-1.6</td>
-    <td class="content">
-     All API Tools plug-ins now have a bundle required execution environment (BREE) of JavaSE-1.6.
-    </td>
-  </tr>
-  <tr id="target-no-preferences">
-    <td class="title">Target platform content is no longer stored in preferences</td>
-    <td class="content">
-     The target platform specified on the <b>Target Platform</b> preference page uses flexible target definitions, stored in .target files,
-     to specify the set of plug-ins PDE should build against and use to launch applications. However, the content of the target platform 
-     was previously stored in preferences. This could lead to inconsistencies between what you expect to exist in the target platform and 
-     what is actually available. This problem was more noticeable when using a complex target definition containing feature or software 
-     site locations.
-     
-     <p>In Luna, the target platform information is always created from the target definition chosen on the preference
-     page. In addition to reducing inconsistencies in the target, there are performance improvements when interacting with the 
-     target.</p>
-    </td>
-  </tr>
-  <tr id="feature-dialog-contains-plugins">
-    <td class="title">Feature selection dialog filters by plug-ins</td>
-    <td class="content">
-     When entering text into the filter field of the feature selection dialog, features that contain a plug-in matching
-     the filter will be returned. This provides a quick way to add the correct feature to include in a product.
-     <p><img src="images/feature-selection.png" alt="The feature selection dialog"/></p>
-    </td>
-  </tr>
-  <tr id="bundle-exceptions-in-editor">
-    <td class="title">OSGi bundle exceptions are displayed in the manifest editor</td>
-    <td class="content">
-     Certain syntax errors, such as missing a comma between entries in the <code>Require-Bundle</code> header, cause bundle exceptions
-     when PDE tries to add the bundle to an OSGi State. The exceptions are now logged and displayed in the manifest editor.   
-     <p><img src="images/bundle-exception.png" alt="Bundle exception displayed in the manifest editor"/></p>
-    </td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="Equinox">Equinox</td>
-  </tr>
-  <tr id="framework-update">
-    <td class="title">Equinox OSGi framework update</td>
-
-    <td class="content">
-      The Equinox Framework implementation has been updated to implement the latest
-      API available for the upcoming OSGi R6 Core Framework specification 
-      (to be finalized in March 2014).  Most of these
-      were implemented as part of M1 also.  They are mentioned here again because
-      OSGi has made the RFCs publicly available in a git repository as they are
-      being written.  See the links below for the latest RFC documents:
-      <ul>
-         <li> Introduction of Service Scopes to the OSGi Service Registry
-             (<a href="https://github.com/osgi/design/tree/master/rfcs/rfc0195">RFC 195</a>)
-         </li>
-         <li> Improvements of Weaving Hooks
-             (<a href="https://github.com/osgi/design/tree/master/rfcs/rfc0191">RFC 191</a>)
-         </li>
-         <li> Clarification of hooks on the system bundle
-             (<a href="https://github.com/osgi/design/tree/master/rfcs/rfc0198">RFC 198</a>)
-         </li>
-         <li> Native environment namespace
-             (<a href="https://github.com/osgi/design/tree/master/rfcs/rfc0188">RFC 188</a>)
-         </li>
-         <li> Data Transfer Objects
-             (<a href="https://github.com/osgi/design/tree/master/rfcs/rfc0185">RFC 185</a>)
-         </li>
-         <li> Extension Bundle Activators - new to M2
-             (<a href="https://github.com/osgi/design/tree/master/rfcs/rfc0204">RFC 204</a>)
-         </li>
-         <li> Addition of FrameworkWiring.findProviders - no RFC
-         </li>
-      </ul>
-    </td>
-  </tr>
-  <tr id="cm-update">
-    <td class="title">Equinox Configuration Admin update</td>
-
-    <td class="content">
-      The Equinox Configuration Admin implementation has been updated to implement
-      the OSGi Configuration Admin Service Specification version 1.5.  The previous
-      release of Equinox Configuration Admin implemented version 1.3.
-    </td>
-  </tr>
-  <tr id="region-update">
-    <td class="title">Equinox Regions update</td>
-
-    <td class="content">
-      The Equinox Regions implementation has been updated to take advantage
-      of Extension Bundle Activators
-      (<a href="https://github.com/osgi/design/tree/master/rfcs/rfc0204">RFC 204</a>)
-       coming in the OSGi R6 specification.
-      This allows Equinox Regions to insert its isolation model before
-      the framework is launched so that proper region behavior can be
-      established before any bundles are loaded in the framework.
-    </td>
-  </tr>
-  <tr id="metatype-update">
-    <td class="title">Equinox Metatype update</td>
-
-    <td class="content">
-      The Equinox Metatype API has been updated to add the methods to
-      get the minimum and maximum values of an attribute definition.
-      (see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=416640">bug 416640</a>)
-    </td>
-  </tr>
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Luna milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.4M1-201308072000/news/">New for Eclipse Luna milestone build M1 (August 9, 2013)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.4/M2/images/bundle-exception.png b/platform/4.4/M2/images/bundle-exception.png
deleted file mode 100644
index e97fa09..0000000
--- a/platform/4.4/M2/images/bundle-exception.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M2/images/feature-selection.png b/platform/4.4/M2/images/feature-selection.png
deleted file mode 100644
index ef123a6..0000000
--- a/platform/4.4/M2/images/feature-selection.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M2/images/move-persp-items.png b/platform/4.4/M2/images/move-persp-items.png
deleted file mode 100644
index 574629a..0000000
--- a/platform/4.4/M2/images/move-persp-items.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M2/images/tag-visibility.png b/platform/4.4/M2/images/tag-visibility.png
deleted file mode 100644
index a888968..0000000
--- a/platform/4.4/M2/images/tag-visibility.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M3/default_style.css b/platform/4.4/M3/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.4/M3/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.4/M3/eclipse-news-M3.html b/platform/4.4/M3/eclipse-news-M3.html
deleted file mode 100644
index b418d13..0000000
--- a/platform/4.4/M3/eclipse-news-M3.html
+++ /dev/null
@@ -1,144 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Project 4.4 M3 News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.4 M3 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M3 
-  (November 1, 2013) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#PDE">PDE</a></li>
-  <li><a href="#Equinox">Equinox</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-
-  <tr id="gtk3-as-default"> 
-    <td class="title">GTK+ 3 used by default</td>
-    <td class="content">
-      SWT and Eclipse will now use the GTK+ 3 libraries by default on all Linux/Unix platforms,
-      whenever GTK+ 3 is installed and available. Previously SWT defaulted to using GTK+ 2.
-      <p>The GTK+ 3 port of SWT is still early access and you can force Eclipse to use the 
-      more stable GTK+2 port by setting the environment variable SWT_GTK3 to 0, if needed.
-      (For example: export SWT_GTK3=0) </p>
-    </td>
-  </tr>
-
-  <tr id="styled-text-api"> 
-    <td class="title">Added new API in StyledText to get text selection state</td>
-    <td class="content">
-      <code>StyledText.isTextSelected()</code> can be used to quickly determine whether any text
-      in the widget is selected or not.
-    </td>
-  </tr>
-
-  <tr id="import-filter-conflicts"> 
-    <td class="title">Filter conflicting projects during import</td>
-    <td class="content">
-      When importing existing projects, you can now filter out any
-      conflicting projects (projects that are already present in your workspace).
-      <p><img src="images/import-filter-conflicts-before.png" alt="filter conflicting projects"/></p>
-    </td>
-  </tr>
-
-  <tr id="batik-1-7">
-    <td class="title">Updated to Batik 1.7</td>
-    <td class="content">The Platform now includes a newer version of Apache Batik, version 1.7.0. 
-    This new version is being used for CSS parsing in the declarative styling engine, and is 
-    notably faster than the previous version.
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="PDE">PDE</td>
-  </tr>
-
-  <tr id="api-tools-annotations">
-    <td class="title">Annotation support in API Tools</td>
-    <td class="content">
-          API Tools now provides support for using annotations to describe your API usage. Prior to the new annotation support you would have, for example,
-          used the <code>&#64;noreference</code> Javadoc tag to indicate noone should use the tagged type / member. Now you can add the <code>&#64;NoReference</code>
-          annotation (in Java 1.5+ source) to the member directly without the need for Javadoc.
-      <img src="images/annotation-example.png" alt="The &#64;NoExtend annotation being used on a class"/>
-      <p>
-        To make the transition from Javadoc tags to the new annotation support, API Tools provides a conversion wizard that is found 
-        using the <strong>Plug-in Tools &gt; Convert API Tools Javadoc tags...</strong> command for a selected project. The wizard can convert all existing Javadoc tags to their annotation
-        equivalent, update the <code>build.properties</code> file and optionally remove all of the old Javadoc tags.
-      </p>
-      <img src="images/javadoc-conversion.png" alt="The Javadoc conversion wizard"/>
-    </td>
-  </tr>
-
-  <tr id="target-status">
-    <td class="title">Updated target platform state in the status bar</td>
-    <td class="content">
-          In 4.4 M2 you could add the target platform indicator to the status bar allowing easy access to the preferences to customize it. Now this 
-          indicator has been updated to show problems with the target platform (if any). The state of the target platform is immediately apparent based on its 
-          icon / decoration and any problems are added to the tooltip.
-      <img src="images/target-status.png" alt="The target platform state in the status bar showing an error"/>
-    </td>
-  </tr>
-
-  <tr>
-    <td colspan="2" class="section" id="Equinox">Equinox</td>
-  </tr>
-
-  <tr id="framework-update">
-    <td class="title">Equinox OSGi framework update</td>
-
-    <td class="content">
-      The Equinox Framework implementation has been updated to implement the latest
-      API available for the upcoming OSGi R6 Core Framework specification 
-      (to be finalized in March 2014).  See 
-      <a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.4M2-201309182000/news/#Equinox">Equinox M2 News</a>
-      for the complete list.  The following had some additional functionality added since M2:
-      <ul>
-         <li> Clarification of hooks on the system bundle
-             (<a href="https://github.com/osgi/design/tree/master/rfcs/rfc0198">RFC 198</a>).
-             The framework must honor the results of bundle collision hooks when the system
-             bundle context is used to install bundles.
-         </li>
-         <li> Extension Bundle Activators
-             (<a href="https://github.com/osgi/design/tree/master/rfcs/rfc0204">RFC 204</a>).
-             New API added to allow the Framework to be initialized with a list of
-             framework listeners that can capture errors that occur while initializing the
-             framework.
-         </li>
-      </ul>
-    </td>
-  </tr>
-  <tr id="region-update">
-    <td class="title">Equinox Regions update</td>
-
-    <td class="content">
-      The Equinox Regions has added a new namespace for sharing bundle lifecycle 
-      operations between regions.  In previous versions of Equinox regions the only way 
-      to share bundle lifecycle operations across different regions was to share complete
-      bundles which also shared all capabilities provided by the bundle.  Now it is
-      possible to use the org.eclipse.equinox.allow.bundle.lifecycle namespace to share
-      only the bundle lifecycle operations between different regions.
-      (see <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=418224">bug 418224</a>)
-    </td>
-  </tr>
-
-  <tr> 
-    <td colspan="2">  </td>
-  </tr>
-</table>
-<p>The above features are just the ones that are new since the previous milestone
-build. Summaries for earlier Luna milestone builds:</p>
-<ul>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.4M2-201309182000/news/">New for Eclipse Luna milestone build M2 (September 20, 2013)</a></li>
-  <li><a href="http://download.eclipse.org/eclipse/downloads/drops4/S-4.4M1-201308072000/news/">New for Eclipse Luna milestone build M1 (August 9, 2013)</a></li>
-</ul>
-</body>
-</html>
diff --git a/platform/4.4/M3/images/annotation-example.png b/platform/4.4/M3/images/annotation-example.png
deleted file mode 100644
index cf0f4e9..0000000
--- a/platform/4.4/M3/images/annotation-example.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M3/images/import-filter-conflicts-before.png b/platform/4.4/M3/images/import-filter-conflicts-before.png
deleted file mode 100644
index c61f61c..0000000
--- a/platform/4.4/M3/images/import-filter-conflicts-before.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M3/images/javadoc-conversion.png b/platform/4.4/M3/images/javadoc-conversion.png
deleted file mode 100644
index 972cec3..0000000
--- a/platform/4.4/M3/images/javadoc-conversion.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M3/images/target-status.png b/platform/4.4/M3/images/target-status.png
deleted file mode 100644
index 8e0b6c2..0000000
--- a/platform/4.4/M3/images/target-status.png
+++ /dev/null
Binary files differ
diff --git a/platform/4.4/M4/default_style.css b/platform/4.4/M4/default_style.css
deleted file mode 100644
index a182540..0000000
--- a/platform/4.4/M4/default_style.css
+++ /dev/null
@@ -1,21 +0,0 @@
-p, table, td, th {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-pre {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-h2 { font-family: verdana, arial, helvetica, geneva; font-size: 18pt; font-weight: bold ; line-height: 14px}
-code {  font-family: "Courier New", Courier, mono; font-size: 10pt}
-sup {  font-family: verdana, arial, helvetica, geneva; font-size: 10px}
-h3 {  font-family: verdana, arial, helvetica, geneva; font-size: 14pt; font-weight: bold}
-li {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt}
-h1 {  font-family: verdana, arial, helvetica, geneva; font-size: 24pt; font-weight: bold}
-body {  font-family: verdana, arial, helvetica, geneva; font-size: 10pt; margin-top: 5mm; margin-left: 3mm}
-.indextop { font-size: x-large; font-family: verdana, arial, helvetica, sans-serif; font-weight: bold}
-.indexsub { font-size: xx-small; font-family: verdana, arial, helvetica, sans-serif; color: #8080FF}
-a.bar:link {  text-decoration: none; color: #FFFFFF}
-a.bar:visited {  color: #FFFFFF; text-decoration: none}
-a.bar:hover {  color: #FFFFFF; text-decoration: underline}
-a.bar {  color: #FFFFFF}
-
-table.news td {border-top: solid thin black;}
-table.news tr {vertical-align: top;}
-table.news tr td.section {font-size: 20px; font-weight: bold;}
-table.news tr td.title {vertical-align: top; width: 30%; font-weight: bold;}
-table.news tr td.content {vertical-align: top; width: 70%;}
\ No newline at end of file
diff --git a/platform/4.4/M4/eclipse-news-M4.html b/platform/4.4/M4/eclipse-news-M4.html
deleted file mode 100644
index 5a2aba8..0000000
--- a/platform/4.4/M4/eclipse-news-M4.html
+++ /dev/null
@@ -1,136 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<meta http-equiv="Content-Language" content="en-us" />
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
-<link rel="stylesheet" href="default_style.css" type="text/css" title="main" media="screen" />
-<title>Eclipse Project 4.4 M4 News</title>
-</head>
-<body>
-<h1>Eclipse Project 4.4 M4 - New and Noteworthy</h1>
-<p>Here are some of the more noteworthy things available in milestone build M4 
-  (December 13, 2013) which is now available for <a href="http://download.eclipse.org/eclipse/downloads/" target="_top">download</a>.
-  <br/>
-  We also recommend to read the Tips and Tricks, either via <b>Help &gt; Tips and Tricks...</b> or online for
-  <a href="http://help.eclipse.org/topic/org.eclipse.platform.doc.user/tips/platform_tips.html">Platform</a>,
-  <a href="http://help.eclipse.org/topic/org.eclipse.jdt.doc.user/tips/jdt_tips.html">JDT</a>, and
-  <a href="http://help.eclipse.org/topic/org.eclipse.pde.doc.user/tips/pde_tips.htm">PDE</a>.
-</p>
-<ul>
-  <li><a href="#Platform">Platform</a></li>
-  <li><a href="#JDT">JDT</a></li>
-  <li><a href="#Equinox">Equinox</a></li>
-</ul>
-
-<table class="news" border="0" cellpadding="10" cellspacing="0" width="80%">
-  <tr>
-    <td colspan="2" class="section" id="Platform">Platform</td>
-  </tr>
-   <tr id="split-editors"> 
-    <td class="title">Split Editors</td>
-    <td class="content">
-     Finally, <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=8009">Bug 8009</a> has been addressed! You can now split / unsplit
-     the currently active editor. Just use one of the new key bindings
-     supplied in Luna M4:
-     <ul>
-     <li><b>Ctrl+_</b> splits the editor one above the other</li>
-     <li><b>Ctrl+{</b> splits the editor side by side</li>
-     <li>Re-applying the command to an already split editor reverts it to only have one pane.</li>
-     </ul>
-    <p><img src="images/split_editors.png" alt=""/></p>
-    <p>Try it out on <i>your</i> favorite editor!</p>
-    </td>
-  </tr>
-  <tr id="swt-needs-1.5"> 
-    <td class="title">SWT requires JRE 1.5</td>
-    <td class="content">
-      The SWT project has moved to Java 1.5 compliance level. SWT applications will now require JRE 1.5 or higher to run.
-    </td>
-  </tr>
-  <tr>
-    <td colspan="2" class="section" id="JDT">JDT</td>
-  </tr>
-  <tr id="beta-java8"> 
-    <td class="title">Java&trade; 8 feature patch</td>
-    <td class="content">
-        The Eclipse support for Java&trade; 8 is making very good progress. Interested parties can take a sneak preview using the following
-        <a href="https://wiki.eclipse.org/JDT/Eclipse_Java_8_Support_%28BETA%29"> install instructions</a>.
-    </td>
-  </tr>
-  <tr id="ecj-needs-1.5"> 
-    <td class="title">ECJ requires 1.6 JRE</td>
-    <td class="content">
-     The JDT Core projec