bundles/org.eclipse.platform.doc.user/whatsNew/platform_whatsnew.html - platform/eclipse.platform.common - Git at Google

 <!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) Eclipse contributors and others 2018, 2019. 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=UTF-8"/>
 <link rel="STYLESHEET" href="../book.css" type="text/css"/>
 <style type="text/css">
 body {max-width: 900px;}
 table.news col.title {width: 30%;}
 /*img {max-width: 520px;}*/
 table.news {table-layout: fixed; border-collapse: collapse; width: 100%;}
 table.news td {border-top: solid thin black; padding: 10px; overflow: visible;}
 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; font-weight: bold;}
 table.news tr td.content {vertical-align: top;}
 ul {padding-left: 13px;}
 </style>
 <title>Eclipse Platform What's New in 4.14</title>
 </head>

 <body>
 <h2>What's New in Eclipse 4.14 (Platform)</h2>
 <p>Here are descriptions of some of the more interesting or significant changes
 made to the Eclipse Platform for the 4.14 release of Eclipse. They are grouped into:</p>
 <ul><!-- NOTE: Sync ../topics_WhatsNew.xml with this! -->
 	<li><a href="#ViewsAndDialogs">Views, Dialogs and Toolbar</a></li>
 	<li><a href="#TextEditors">Text Editors</a></li>
 	<li><a href="#Debug">Debug</a></li>
 	<li><a href="#StylingThemes">Themes and Styling</a></li>
 	<li><a href="#GeneralUpdates">General Updates</a></li>
 </ul>
 <p>
 Plug-in developers will also be interested in the corresponding
 <a href="../../org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html">What's new</a>
 document in the plug-in developer's guide.</p>
 <p>We also recommend to read the <a href="../tips/platform_tips.html">Tips and Tricks</a>.</p>
 <br/>

 <!-- ****************** START OF N&N TABLE ****************** -->
 <table class="news">
 <colgroup>
   <col class="title" />
   <col />
 </colgroup>
 <tbody>
   <!-- ******************* Views, Dialogs and Toolbar ************************************* -->
   <tr>
     <td id="ViewsAndDialogs" class="section" colspan="2">
     <h2>Views, Dialogs and Toolbar </h2>
     </td>
   </tr>

   <tr id="new-view-menu-icon"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551604 -->
     <td class="title">New view menu icon</td>
     <td class="content">
        The view menu chevron icon (<small><small>&#9661;</small></small>) is replaced by a modern equivalent, the vertical ellipsis ( <b>&#10247;</b>).
        <p>
          Almost every view has a menu that may contain additional configuration settings like filters, layout settings, and so on. The view menu was often
          overlooked and we expect that this change will help users to find it.
        </p>
        <br/>
        <img src="images/view_menu.png" alt="View Menu with vertical ellipsis icon highlighted"/><br/><br/>
     </td>
   </tr>

   <tr id="quick-access-improvements"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551970 -->
     <td class="title">Find Actions: The improved Quick Access</td>
     <td class="content">
        The formerly called <b>Quick Access</b> action has been retitled to <b>Find Actions</b> to better emphasize its goal.<br/><br/>
        The related UI has changed a bit to improve its usage and accessibility:
        <ul>
          <li>The widget item is now a regular toolbar item (button-like)</li>
          <li>An icon is shown</li>
          <li>Right-clicking on the tool item works and shows typical actions, including <b>Hide</b></li>
          <li>The proposals are now a regular dialog, centered on the workbench</li>
        </ul>
        These changes will greatly improve the experience if you're using a screen reader as it relies on a more standardized focus state. This also
        leverages all the default and usual accessibility features of dialogs (moveable, resizable...).
        <p>Loading the proposals has been improved as well to avoid UI freezes when loading proposals.</p>
     </td>
   </tr>

   <tr id="quick-text-search-in-Find-Actions"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551970 -->
     <td class="title">Find Actions finds text in file contents</td>
     <td class="content">
        <b>Find Actions</b> is now extended by the <b>Quick Text Search</b> feature to show the potential
        text matches in file contents also in the proposals.
        <p>
          <img src="images/file-content-find-action.png" alt=""/>
        </p>
       <p>
       If the Quick Text Search bundle wasn't started yet, you may miss those matches. In this case, you can use <b>Find Actions</b> itself
       to activate the Quick Text Search by finding and selecting the <b>Activate bundle for 'File content' proposals</b> entry.
       </p>
       <p>
         <img src="images/activate-file-content.png" alt="Activate File Contents"/>
       </p>
     </td>
   </tr>

   <tr id="open-file-find-actions"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=552714 -->
     <td class="title">Find Actions lists workspace files</td>
     <td class="content">
        <b>Find Actions</b> can now list matching file names from the workspace (similar to the <b>Open Resource</b> dialog).
        Upon selection the file is opened in the editor.
        <p>
          <img src="images/find-actions-resources.png" alt=""/>
        </p>
     </td>
   </tr>

  <tr id="project-explorer-inline-rename"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=550560 -->
     <td class="title">
             Inline rename for simple resources while in Project Explorer.
     </td>
     <td class="content">
      In the <b>Project Explorer</b>, renaming (with the <b><code>F2</code></b> shortcut or Rename context menu) will start an inline rename for normal resources when other files aren't affected by the rename.
      <p>
       <img src="images/project-explorer-inline-renaming.png" alt="" />
      </p>
      <p>
       In cases where other files are affected by the rename, or the rename operation is customized, the rename dialog will appear as it previously did.
      </p>
     </td>
   </tr>
   <!-- ******************* End of Views, Dialogs and Toolbar ************************************* -->

   <!-- ******************* Text Editors ************************************* -->
   <tr>
     <td id="TextEditors" class="section" colspan="2">
     <h2>Text Editors </h2>
     </td>
   </tr>

   <tr id="show-markers-as-code-minings"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=547665 -->
     <td class="title">Show problem markers inline</td>
     <td class="content">
       You can now see the <b>errors, warnings, and info markers</b> inline in most of the text editors.
       No more mousing around to see the actual error message!
       <p>
         <img src="images/annotation-code-mining-jdt.png" alt="Java editor showing a warning and an error inline"/>
       </p>
       <p>
         You can see the available quick-fixes by clicking on the message.
       </p>
       <p>
         <img src="images/annotation-code-mining-quickfix.png" alt="Manifest editor the quick-fix menu for an error displayed inline"/>
       </p>
       <p>
         You can enable it on preference page <b>General &gt; Editors &gt; Text Editors</b> and set <b>Show Code Minings for Annotations</b> to:
       </p>
       <ul>
         <li>None (default)</li>
         <li>Error</li>
         <li>Errors / Warnings</li>
         <li>Errors / Warnings /Info</li>
       </ul>
     </td>
   </tr>

   <tr id="delete-spaces-as-tabs"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=483846 -->
     <td class="title">Backspace/delete can treat spaces as tabs</td>
     <td class="content">
       If you use the <b>Insert spaces for tabs</b> option, now you can also change the backspace and delete keys behavior to remove multiple spaces at once, as if they were a tab.
       <p>
        The new setting is called <b>Remove multiple spaces on backspace/delete</b> and is found on the <b>General &gt; Editors &gt; Text Editors</b> preference page.
       </p>
       <p>
         <img src="images/delete-spaces-as-tabs.png" alt="Text editors preference page"/>
       </p>
     </td>
   </tr>
   <!-- ******************* End of Text Editors ************************************* -->

   <!-- ****************** Debug ************************************* -->
   <tr>
     <td id="Debug" class="section" colspan="2">
     <h2>Debug </h2>
     </td>
   </tr>

   <tr id="collapse-all-debug-view"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=498365 -->
     <td class="title">Collapse All Button in the Debug View</td>
     <td class="content">
       In the <b>Debug</b> View, now you can now use the new <b>Collapse All</b> button to collapse all the launches.
       <p>
         Before collapsing:
       </p>
       <p>
        <img src="images/collapse-all-debug-view-before.png" alt=""/>
       </p>
       <p>
         After collapsing:
       </p>
       <p>
        <img src="images/collapse-all-debug-view-after.png" alt=""/>
       </p>
     </td>
   </tr>

   <tr id="control-character-console"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=76936 -->
     <td class="title">Control character interpretation in Console View</td>
     <td class="content">
       The <b>Console</b> View can now interpret the control characters backslash (<code>\b</code>) and
       carriage return (<code>\r</code>).
       <p>
        This feature is disabled by default. You can enable it on the <b>Run/Debug &gt; Console</b> preference
        page.
       </p>
     </td>
   </tr>
   <!-- ****************** End of Debug ************************************* -->

   <!-- ****************** Preferences ************************************* -->
   <!--
   <tr>
     <td id="Preferences" class="section" colspan="2">
     <h2>Preferences </h2>
     </td>
   </tr>
   -->
   <!-- ****************** End of Preferences ************************************* -->

   <!-- ******************* Themes and Styling ************************************* -->
   <tr>
     <td id="StylingThemes" class="section" colspan="2">
     <h2>Themes and Styling </h2>
     </td>
   </tr>

     <tr id="ui-forms-styling"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549916 -->
     <td class="title">Improvements in UI Forms Styling</td>
     <td class="content">
       CSS customization of <code>ExpandableComposite</code> and <code>Section</code> was reworked to give you more control over their styling.
       In dark mode, those elements now integrate better with other Form elements.
       <p>Old:</p>
       <p>
         <img src="images/pom_dark_old.png" alt=""/>
       </p>
       <p>New:</p>
       <p>
         <img src="images/pom_dark_new.png" alt=""/>
       </p>
     </td>
   </tr>

   <tr id="perspective-switcher"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551390 -->
     <td class="title">Perspective switcher gets aligned with normal toolbar styling </td>
     <td class="content">
     	The special styling of the <b>Perspective switcher</b> has been removed to make the Toolbar look
     	consistent. This also reduces OS specific styling issues with the perspective switcher.
       <p>Old:</p>
       <p>
         <img src="images/old-perspective-switcher.png" alt=""/>
       </p>
       <p>New:</p>
       <p>
         <img src="images/new-perspective-switcher.png" alt=""/>
       </p>
     </td>
   </tr>

  <tr id="dark-colors-usage"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551707 -->
     <td class="title">Usage of consistent colors for the dark theme</td>
     <td class="content">
       The usage of different shades of gray in the dark theme was reduced.
       <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551707 -->
       <p>The styling of the widgets is also not based on the selected view anymore, which makes the UI more consistent.</p>
      </td>
   </tr>

   <!-- ******************* End of Themes and Styling ************************************* -->

   <!-- ******************* General Updates ************************************* -->
   <tr>
     <td id="GeneralUpdates" class="section" colspan="2">
     <h2>General Updates </h2>
     </td>
   </tr>

   <tr id="ant-version-upgrade"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=550793 -->
     <td class="title">Ant 1.10.7</td>
     <td class="content">
       Eclipse has adopted Ant version 1.10.7.
     </td>
   </tr>

   <tr id="ant-ui-support-for-include-task"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=412809 -->
     <td class="title">Support for the Ant include task added</td>
     <td class="content">
       The Ant <code>include</code> task (available in the Ant library since 1.8.0) is now fully recognized by the ant-ui-plugin and validated accordingly.
     </td>
   </tr>

   <!-- ******************* End of General Updates ************************************* -->
 </tbody>
 </table>
 <!-- ****************** END OF N&N TABLE ****************** -->

 </body>
 </html>
	<!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) Eclipse contributors and others 2018, 2019. 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=UTF-8"/>
	<link rel="STYLESHEET" href="../book.css" type="text/css"/>
	<style type="text/css">
	body {max-width: 900px;}
	table.news col.title {width: 30%;}
	/img {max-width: 520px;}/
	table.news {table-layout: fixed; border-collapse: collapse; width: 100%;}
	table.news td {border-top: solid thin black; padding: 10px; overflow: visible;}
	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; font-weight: bold;}
	table.news tr td.content {vertical-align: top;}
	ul {padding-left: 13px;}
	</style>
	<title>Eclipse Platform What's New in 4.14</title>
	</head>

	<body>
	<h2>What's New in Eclipse 4.14 (Platform)</h2>
	<p>Here are descriptions of some of the more interesting or significant changes
	made to the Eclipse Platform for the 4.14 release of Eclipse. They are grouped into:</p>
	<ul><!-- NOTE: Sync ../topics_WhatsNew.xml with this! -->
	<li><a href="#ViewsAndDialogs">Views, Dialogs and Toolbar</a></li>
	<li><a href="#TextEditors">Text Editors</a></li>
	<li><a href="#Debug">Debug</a></li>
	<li><a href="#StylingThemes">Themes and Styling</a></li>
	<li><a href="#GeneralUpdates">General Updates</a></li>
	</ul>
	<p>
	Plug-in developers will also be interested in the corresponding
	<a href="../../org.eclipse.platform.doc.isv/whatsNew/platform_isv_whatsnew.html">What's new</a>
	document in the plug-in developer's guide.</p>
	<p>We also recommend to read the <a href="../tips/platform_tips.html">Tips and Tricks</a>.</p>
	<br/>

	<!-- **************** START OF N&N TABLE **************** -->
	<table class="news">
	<colgroup>
	<col class="title" />
	<col />
	</colgroup>
	<tbody>
	<!-- ***************** Views, Dialogs and Toolbar *********************************** -->
	<tr>
	<td id="ViewsAndDialogs" class="section" colspan="2">
	<h2>Views, Dialogs and Toolbar </h2>
	</td>
	</tr>

	<tr id="new-view-menu-icon"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551604 -->
	<td class="title">New view menu icon</td>
	<td class="content">
	The view menu chevron icon (<small><small>▽</small></small>) is replaced by a modern equivalent, the vertical ellipsis ( <b>⠇</b>).
	<p>
	Almost every view has a menu that may contain additional configuration settings like filters, layout settings, and so on. The view menu was often
	overlooked and we expect that this change will help users to find it.
	</p>
	<br/>
	<img src="images/view_menu.png" alt="View Menu with vertical ellipsis icon highlighted"/><br/><br/>
	</td>
	</tr>

	<tr id="quick-access-improvements"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551970 -->
	<td class="title">Find Actions: The improved Quick Access</td>
	<td class="content">
	The formerly called <b>Quick Access</b> action has been retitled to <b>Find Actions</b> to better emphasize its goal.<br/><br/>
	The related UI has changed a bit to improve its usage and accessibility:
	<ul>
	<li>The widget item is now a regular toolbar item (button-like)</li>
	<li>An icon is shown</li>
	<li>Right-clicking on the tool item works and shows typical actions, including <b>Hide</b></li>
	<li>The proposals are now a regular dialog, centered on the workbench</li>
	</ul>
	These changes will greatly improve the experience if you're using a screen reader as it relies on a more standardized focus state. This also
	leverages all the default and usual accessibility features of dialogs (moveable, resizable...).
	<p>Loading the proposals has been improved as well to avoid UI freezes when loading proposals.</p>
	</td>
	</tr>

	<tr id="quick-text-search-in-Find-Actions"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551970 -->
	<td class="title">Find Actions finds text in file contents</td>
	<td class="content">
	<b>Find Actions</b> is now extended by the <b>Quick Text Search</b> feature to show the potential
	text matches in file contents also in the proposals.
	<p>
	<img src="images/file-content-find-action.png" alt=""/>
	</p>
	<p>
	If the Quick Text Search bundle wasn't started yet, you may miss those matches. In this case, you can use <b>Find Actions</b> itself
	to activate the Quick Text Search by finding and selecting the <b>Activate bundle for 'File content' proposals</b> entry.
	</p>
	<p>
	<img src="images/activate-file-content.png" alt="Activate File Contents"/>
	</p>
	</td>
	</tr>

	<tr id="open-file-find-actions"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=552714 -->
	<td class="title">Find Actions lists workspace files</td>
	<td class="content">
	<b>Find Actions</b> can now list matching file names from the workspace (similar to the <b>Open Resource</b> dialog).
	Upon selection the file is opened in the editor.
	<p>
	<img src="images/find-actions-resources.png" alt=""/>
	</p>
	</td>
	</tr>

	<tr id="project-explorer-inline-rename"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=550560 -->
	<td class="title">
	Inline rename for simple resources while in Project Explorer.
	</td>
	<td class="content">
	In the <b>Project Explorer</b>, renaming (with the <b><code>F2</code></b> shortcut or Rename context menu) will start an inline rename for normal resources when other files aren't affected by the rename.
	<p>
	<img src="images/project-explorer-inline-renaming.png" alt="" />
	</p>
	<p>
	In cases where other files are affected by the rename, or the rename operation is customized, the rename dialog will appear as it previously did.
	</p>
	</td>
	</tr>
	<!-- ***************** End of Views, Dialogs and Toolbar *********************************** -->

	<!-- ***************** Text Editors *********************************** -->
	<tr>
	<td id="TextEditors" class="section" colspan="2">
	<h2>Text Editors </h2>
	</td>
	</tr>

	<tr id="show-markers-as-code-minings"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=547665 -->
	<td class="title">Show problem markers inline</td>
	<td class="content">
	You can now see the <b>errors, warnings, and info markers</b> inline in most of the text editors.
	No more mousing around to see the actual error message!
	<p>
	<img src="images/annotation-code-mining-jdt.png" alt="Java editor showing a warning and an error inline"/>
	</p>
	<p>
	You can see the available quick-fixes by clicking on the message.
	</p>
	<p>
	<img src="images/annotation-code-mining-quickfix.png" alt="Manifest editor the quick-fix menu for an error displayed inline"/>
	</p>
	<p>
	You can enable it on preference page <b>General > Editors > Text Editors</b> and set <b>Show Code Minings for Annotations</b> to:
	</p>
	<ul>
	<li>None (default)</li>
	<li>Error</li>
	<li>Errors / Warnings</li>
	<li>Errors / Warnings /Info</li>
	</ul>
	</td>
	</tr>

	<tr id="delete-spaces-as-tabs"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=483846 -->
	<td class="title">Backspace/delete can treat spaces as tabs</td>
	<td class="content">
	If you use the <b>Insert spaces for tabs</b> option, now you can also change the backspace and delete keys behavior to remove multiple spaces at once, as if they were a tab.
	<p>
	The new setting is called <b>Remove multiple spaces on backspace/delete</b> and is found on the <b>General > Editors > Text Editors</b> preference page.
	</p>
	<p>
	<img src="images/delete-spaces-as-tabs.png" alt="Text editors preference page"/>
	</p>
	</td>
	</tr>
	<!-- ***************** End of Text Editors *********************************** -->

	<!-- **************** Debug *********************************** -->
	<tr>
	<td id="Debug" class="section" colspan="2">
	<h2>Debug </h2>
	</td>
	</tr>

	<tr id="collapse-all-debug-view"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=498365 -->
	<td class="title">Collapse All Button in the Debug View</td>
	<td class="content">
	In the <b>Debug</b> View, now you can now use the new <b>Collapse All</b> button to collapse all the launches.
	<p>
	Before collapsing:
	</p>
	<p>
	<img src="images/collapse-all-debug-view-before.png" alt=""/>
	</p>
	<p>
	After collapsing:
	</p>
	<p>
	<img src="images/collapse-all-debug-view-after.png" alt=""/>
	</p>
	</td>
	</tr>

	<tr id="control-character-console"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=76936 -->
	<td class="title">Control character interpretation in Console View</td>
	<td class="content">
	The <b>Console</b> View can now interpret the control characters backslash (<code>\b</code>) and
	carriage return (<code>\r</code>).
	<p>
	This feature is disabled by default. You can enable it on the <b>Run/Debug > Console</b> preference
	page.
	</p>
	</td>
	</tr>
	<!-- **************** End of Debug *********************************** -->

	<!-- **************** Preferences *********************************** -->
	<!--
	<tr>
	<td id="Preferences" class="section" colspan="2">
	<h2>Preferences </h2>
	</td>
	</tr>
	-->
	<!-- **************** End of Preferences *********************************** -->

	<!-- ***************** Themes and Styling *********************************** -->
	<tr>
	<td id="StylingThemes" class="section" colspan="2">
	<h2>Themes and Styling </h2>
	</td>
	</tr>

	<tr id="ui-forms-styling"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=549916 -->
	<td class="title">Improvements in UI Forms Styling</td>
	<td class="content">
	CSS customization of <code>ExpandableComposite</code> and <code>Section</code> was reworked to give you more control over their styling.
	In dark mode, those elements now integrate better with other Form elements.
	<p>Old:</p>
	<p>
	<img src="images/pom_dark_old.png" alt=""/>
	</p>
	<p>New:</p>
	<p>
	<img src="images/pom_dark_new.png" alt=""/>
	</p>
	</td>
	</tr>

	<tr id="perspective-switcher"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551390 -->
	<td class="title">Perspective switcher gets aligned with normal toolbar styling </td>
	<td class="content">
	The special styling of the <b>Perspective switcher</b> has been removed to make the Toolbar look
	consistent. This also reduces OS specific styling issues with the perspective switcher.
	<p>Old:</p>
	<p>
	<img src="images/old-perspective-switcher.png" alt=""/>
	</p>
	<p>New:</p>
	<p>
	<img src="images/new-perspective-switcher.png" alt=""/>
	</p>
	</td>
	</tr>

	<tr id="dark-colors-usage"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551707 -->
	<td class="title">Usage of consistent colors for the dark theme</td>
	<td class="content">
	The usage of different shades of gray in the dark theme was reduced.
	<!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=551707 -->
	<p>The styling of the widgets is also not based on the selected view anymore, which makes the UI more consistent.</p>
	</td>
	</tr>

	<!-- ***************** End of Themes and Styling *********************************** -->

	<!-- ***************** General Updates *********************************** -->
	<tr>
	<td id="GeneralUpdates" class="section" colspan="2">
	<h2>General Updates </h2>
	</td>
	</tr>

	<tr id="ant-version-upgrade"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=550793 -->
	<td class="title">Ant 1.10.7</td>
	<td class="content">
	Eclipse has adopted Ant version 1.10.7.
	</td>
	</tr>

	<tr id="ant-ui-support-for-include-task"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=412809 -->
	<td class="title">Support for the Ant include task added</td>
	<td class="content">
	The Ant <code>include</code> task (available in the Ant library since 1.8.0) is now fully recognized by the ant-ui-plugin and validated accordingly.
	</td>
	</tr>

	<!-- ***************** End of General Updates *********************************** -->
	</tbody>
	</table>
	<!-- **************** END OF N&N TABLE **************** -->

	</body>
	</html>