4.7/M1/index.html - gerrit/www.eclipse.org/eclipse/news - 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 http-equiv="Content-Language" content="en-us" />
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
 <link rel="stylesheet" href="style.css" type="text/css" title="main" media="screen" />
 <title>Eclipse Project Oxygen (4.7) M1 News</title>
 </head>
 <body>
 <h1>Eclipse Project Oxygen (4.7) M1 - New and Noteworthy</h1>
 <p>Here are some of the more noteworthy things available in the Oxygen milestone build M1
   which is now available for <a href="http://download.eclipse.org/eclipse/downloads/#4.7_Stable_Builds" 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="#PDE">PDE</a></li>
   <li><a href="#Platform-Dev">Platform Developers</a></li>
   <li><a href="#Equinox">Equinox</a></li>
 </ul>

 <table class="news">
   <colgroup>
     <col class="title" />
     <col />
   </colgroup>


   <tr>
     <td colspan="2" class="section" id="Platform">Platform</td>
   </tr>

   <tr id="unix-platforms-dropped">
     <td class="title">Dropped support for Unix platforms</td>
     <td class="content">
 	  Eclipse has dropped support for the following Unix based platforms: AIX, Solaris, HP-UX and s390.
 	  For these platforms, no builds are available on the eclipse.org downloads page.
 	  <p>
 	  For more information, please read the <a href="https://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg10207.html">announcement</a> made by the Eclipse PMC in July.
 	  </p>
     </td>
   </tr>

    <tr id="always-run-in-background">
     <td class="title">"Always run in background" enabled by default</td>
     <td class="content">
  		The <b>Always run in background</b> preference is now enabled by default.
  		If you prefer to see a progress dialog for long-running operations, you
  		can disable this option on the <b>General</b> preference page.
     </td>
   </tr>

   <tr id="toolbar-improved-default-styling">
     <td class="title">Improved default styling for the toolbar</td>
     <td class="content">
       The styling of the window toolbar has been improved.
       On Windows, the toolbar color is now consistent with the color of the perspective switcher.

       <p>
         <img src="images/css-styles-windows-toolbar.png" alt=""/>
       </p>
       <p>
         On Linux and Mac, the separator line was removed, which gives you a few more pixels on Linux
         and removes a yellow line on the Mac.
       </p>
       <p>
         <img src="images/css-styles-mac-toolbar.png" alt=""/>
       </p>
     </td>
   </tr>

   <tr id="flat-gray-forms-based-styling">
     <td class="title">New default styling for form-based user interfaces</td>
     <td class="content">
       The default styling for form-based user interfaces was changed to use a flat, gray style.
       This change was inspired by the popular "Clean Sheet" plug-in.
       Below you see screenshots of the MANIFEST.MF editor and the Git Staging view in this new design.
       <p>
         <img src="images/forms-grey-styling1.png" alt=""/>
       </p>
       <p>
         <img src="images/forms-grey-styling2.png" alt=""/>
       </p>

     </td>
   </tr>

   <tr id="open-images-in-eclipse">
     <td class="title">Images are opened in the Eclipse IDE</td>
     <td class="content">
       Image files are now opened directly in Eclipse by default.
       The Internal Web Browser has been registered as default editor for files with the png, jpg, jpeg, gif, bmp, and ico extensions.
      <p>
         <img src="images/image-opened-in-eclipse.png" alt=""/>
      </p>
      Use <b>Open With > System Editor</b> to open files in the default external program.
     </td>
   </tr>

   <tr id="copy-build-id-information-in-about-dialog">
     <td class="title">"Copy Build Id Information" in About dialog</td>
     <td class="content">
       In the <b>About</b> dialog, you can use the context menu to copy
       information about your Eclipse installation.
       <p>
         <img src="images/about-dialog-get-build-information.png" alt=""/>
       </p>
       The <b>Copy Build Id Information to Clipboard</b> command copies
       the product name, version, build id, OS, windowing system, and additional
       OS-specific info like the GTK or WebKit versions.
       <p>
         The command can also be invoked via Quick Access <b>Quick Access</b> (<b>Ctrl+3</b>).
       </p>
     </td>
   </tr>

   <tr id="removed-installation-details-menu-entry">
     <td class="title">Installation Details menu entry removed</td>
     <td class="content">
       The <b>Help &gt; Installation Details</b> menu entry has been removed.
       You can access this dialog via <b>Help &gt; About &gt; Installation Details</b> or
       via <b>Quick Access</b> (<b>Ctrl+3</b>) and then typing "Installation Details".
     </td>
   </tr>

   <tr id="maximize-and-minimize-window-appearance">
     <td class="title">Maximize and Minimize via Window &gt; Appearance menu</td>
     <td class="content">
       The <b>Maximize</b> and <b>Minimize Active View or Editor</b> menu items have been moved to
       the <b>Window &gt; Appearance</b> menu. They used to be in the <b>Window &gt; Navigate</b> menu.
     </td>
   </tr>

   <tr id="terminate-relaunch-history">
     <td class="title">"Terminate and Relaunch" from Run menu, context menu and tool bar</td>
     <td class="content">
       A <b>Terminate and Relaunch</b> option is now available while launching from Run menu, context menu and tool bar.
       The default setting is to launch without terminating previous launches. To enable automatic termination,
       select the option <b>Terminate and Relaunch while launching</b> on
       <b>Preferences &gt; Run/Debug &gt; Launching</b>.

       <p>
         The behavior not selected on the preference page can also be activated on-demand by holding
         the <b>Shift</b> key while launching the configuration from history.
       </p>
 	  <p><img src="images/launch-preference-terminate-relaunch.png" alt="" /></p>
     </td>
   </tr>

   <tr id="breakpoint-overview-ruler">
     <td class="title">Breakpoints in Overview Ruler</td>
     <td class="content">
       <b>Breakpoints</b> are now visible in the <b>Overview Ruler</b> by default.
 	  <p><img src="images/breakpoint-overview-ruler.png" alt="" /></p>
 	  To configure the rendering of annotations, right-click the overview ruler and choose <b>Preferences...</b>.
 	  This directly opens the preference page <b>General &gt; Editors &gt; Text Editors &gt; Annotations</b>.
     </td>
   </tr>

   <tr>
     <td colspan="2" class="section" id="JDT">JDT</td>
   </tr>

   <tr id="show-junit-failure-trace-in-console-view">
     <td class="title">Show JUnit failure trace in Console view</td>
     <td class="content">
       A new button has been added to the JUnit Failure Trace header to show the stack trace of a failed JUnit test in the Console view.
       The Console view makes it convenient to view a long and wide stack trace, copy parts of the stack trace and navigate to the classes on the stack trace using hyperlinks.
         <p>
           <img src="images/show-junit-failure-trace-in-console-view.png" alt="" />
         </p>
     </td>
   </tr>

   <tr id="skip-button-in-organize-imports-dialog">
     <td class="title">Skip button in Organize Imports dialog</td>
     <td class="content">
       While using the Organize Imports dialog to import multiple unresolved types, you can now skip a type without cancelling the whole operation by using the new Skip button.
       No import statement is added for the skipped type.
         <p>
           <img src="images/skip-button-in-organize-imports-dialog.png" alt="" />
         </p>
     </td>
   </tr>

   <tr id="type-name-with-extension-in-new-java-type-creation-wizards">
     <td class="title">Type name with extension in New Java Type creation wizards</td>
     <td class="content">
       New Java Type creation wizards now accept the <code>.java</code> extension with the type name instead of showing the error message: "Type name must not be qualified".
       For example, to create a new class <code>com.test.C1&lt;T&gt;.java</code>, you can directly paste this qualified type name with extension in the Name field of the New Java Class wizard.
         <p>
           <img src="images/type-name-with-extension.png" alt="" />
         </p>
     </td>
   </tr>

   <tr>
     <td colspan="2" class="section" id="PDE">PDE</td>
   </tr>

   <tr id="first-item-pde">
     <td class="title">New Layout Spy tool</td>
     <td class="content">
       PDE has added a new tool for debugging SWT layouts. To activate it, use the
       shortcut <b>Ctrl+Alt+Shift+F9</b> from any window.
       <p>Usage:</p>
       <ul>
       <li>Click <b>Select Control</b> then click the control you want to inspect</li>
       <li>Enable <b>Show Overlay</b> and navigate the widget hierarchy until you find a
           control whose boundary is correct (the red rectangle) and whose child's boundary
           is incorrect (the yellow rectangle).</li>
       <li>Look at the results of computeSize. If the result of computeSize is correct,
           the problem is in the parent layout or its attributes. Otherwise the problem
           is in the child widget.</li>
       </ul>
         <p>
           <img src="images/layout-spy.png" alt="" />
         </p>
     </td>
   </tr>

   	<tr id="pde-changed-exec-env-version-problem">
     <td class="title">Changed Execution Environments creates a version problem</td>
     <td class="content">
        Changing the <b>Execution Environments </b> in a plug-in now creates a problem marker indicating that the minor version should be increased. This happens
        if the minor version is not already increased with respect to the baseline. The preference to control the severity of this problem is located in
        the <b>Version Management</b> tab of the <b>Plug-in Development &gt; API Errors/Warnings</b> preference page.
       <p>
         <img src="images/pde-changed-exec-env-version-problem.png" alt=""/>
       </p>
     </td>
   	</tr>

   <tr>
     <td colspan="2" class="section" id="Platform-Dev">Platform Developers</td>
   </tr>

   <tr id="declarative-services-replaceable">
     <td class="title">Declarative services implementation replaceable</td>
     <td class="content">
       In platform bundles, the bundle dependencies to <code>org.eclipse.osgi.services</code> have been replaced with the necessary package imports.
 	  Mostly <code>org.osgi.service.event</code> needed to be added to the imported packages. This was necessary to avoid a
 	  uses constraint violation when replacing <code>org.eclipse.equinox.ds</code> with <code>org.apache.felix.scr</code>.
     </td>
   </tr>

   <tr id="swt-1.8">
     <td class="title">SWT requires 1.8 Java runtime</td>
     <td class="content">
 	  The SWT projects are now compiled at 1.8 compliance level. As a result, a Java runtime of 1.8 or above is required to run SWT applications.
     </td>
   </tr>


   <tr>
     <td colspan="2" class="section" id="Equinox">Equinox</td>
   </tr>

   <tr id="provided-capabilities-metadata">
     <td class="title">Several plug-ins define Provided Capabilities metadata</td>
     <td class="content">
       You can now rely on OSGi's <code>Require-Capability</code> meta data in your Eclipse-based application for
 	  <code>org.eclipse.equinox.event</code> and <code>org.eclipse.equinox.cm</code> as they now provide
 	  the corresponding <code>osgi.service</code> capability.
 	  Additionally, p2 capabilities are specified to be able to configure non-code dependencies that can be interpreted
 	  by the p2 resolver.
     </td>
   </tr>


   <tr>
     <td colspan="2"/>
   </tr>
 </table>

 <!--
 <p>The above features are just the ones that are new since the previous milestone
 build. Summaries for earlier Oxygen milestone builds:</p>
 <ul>
   <li><a href="https://www.eclipse.org/eclipse/news/4.7/M1/">News for Eclipse Oxygen milestone build M1</a></li>
 </ul>
 -->

 </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 http-equiv="Content-Language" content="en-us" />
	<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
	<link rel="stylesheet" href="style.css" type="text/css" title="main" media="screen" />
	<title>Eclipse Project Oxygen (4.7) M1 News</title>
	</head>
	<body>
	<h1>Eclipse Project Oxygen (4.7) M1 - New and Noteworthy</h1>
	<p>Here are some of the more noteworthy things available in the Oxygen milestone build M1
	which is now available for <a href="http://download.eclipse.org/eclipse/downloads/#4.7_Stable_Builds" target="_top">download</a>.
	<br/>
	We also recommend to read the Tips and Tricks, either via <b>Help > 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="#PDE">PDE</a></li>
	<li><a href="#Platform-Dev">Platform Developers</a></li>
	<li><a href="#Equinox">Equinox</a></li>
	</ul>

	<table class="news">
	<colgroup>
	<col class="title" />
	<col />
	</colgroup>


	<tr>
	<td colspan="2" class="section" id="Platform">Platform</td>
	</tr>

	<tr id="unix-platforms-dropped">
	<td class="title">Dropped support for Unix platforms</td>
	<td class="content">
	Eclipse has dropped support for the following Unix based platforms: AIX, Solaris, HP-UX and s390.
	For these platforms, no builds are available on the eclipse.org downloads page.
	<p>
	For more information, please read the <a href="https://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg10207.html">announcement</a> made by the Eclipse PMC in July.
	</p>
	</td>
	</tr>

	<tr id="always-run-in-background">
	<td class="title">"Always run in background" enabled by default</td>
	<td class="content">
	The <b>Always run in background</b> preference is now enabled by default.
	If you prefer to see a progress dialog for long-running operations, you
	can disable this option on the <b>General</b> preference page.
	</td>
	</tr>

	<tr id="toolbar-improved-default-styling">
	<td class="title">Improved default styling for the toolbar</td>
	<td class="content">
	The styling of the window toolbar has been improved.
	On Windows, the toolbar color is now consistent with the color of the perspective switcher.

	<p>
	<img src="images/css-styles-windows-toolbar.png" alt=""/>
	</p>
	<p>
	On Linux and Mac, the separator line was removed, which gives you a few more pixels on Linux
	and removes a yellow line on the Mac.
	</p>
	<p>
	<img src="images/css-styles-mac-toolbar.png" alt=""/>
	</p>
	</td>
	</tr>

	<tr id="flat-gray-forms-based-styling">
	<td class="title">New default styling for form-based user interfaces</td>
	<td class="content">
	The default styling for form-based user interfaces was changed to use a flat, gray style.
	This change was inspired by the popular "Clean Sheet" plug-in.
	Below you see screenshots of the MANIFEST.MF editor and the Git Staging view in this new design.
	<p>
	<img src="images/forms-grey-styling1.png" alt=""/>
	</p>
	<p>
	<img src="images/forms-grey-styling2.png" alt=""/>
	</p>

	</td>
	</tr>

	<tr id="open-images-in-eclipse">
	<td class="title">Images are opened in the Eclipse IDE</td>
	<td class="content">
	Image files are now opened directly in Eclipse by default.
	The Internal Web Browser has been registered as default editor for files with the png, jpg, jpeg, gif, bmp, and ico extensions.
	<p>
	<img src="images/image-opened-in-eclipse.png" alt=""/>
	</p>
	Use <b>Open With > System Editor</b> to open files in the default external program.
	</td>
	</tr>

	<tr id="copy-build-id-information-in-about-dialog">
	<td class="title">"Copy Build Id Information" in About dialog</td>
	<td class="content">
	In the <b>About</b> dialog, you can use the context menu to copy
	information about your Eclipse installation.
	<p>
	<img src="images/about-dialog-get-build-information.png" alt=""/>
	</p>
	The <b>Copy Build Id Information to Clipboard</b> command copies
	the product name, version, build id, OS, windowing system, and additional
	OS-specific info like the GTK or WebKit versions.
	<p>
	The command can also be invoked via Quick Access <b>Quick Access</b> (<b>Ctrl+3</b>).
	</p>
	</td>
	</tr>

	<tr id="removed-installation-details-menu-entry">
	<td class="title">Installation Details menu entry removed</td>
	<td class="content">
	The <b>Help > Installation Details</b> menu entry has been removed.
	You can access this dialog via <b>Help > About > Installation Details</b> or
	via <b>Quick Access</b> (<b>Ctrl+3</b>) and then typing "Installation Details".
	</td>
	</tr>

	<tr id="maximize-and-minimize-window-appearance">
	<td class="title">Maximize and Minimize via Window > Appearance menu</td>
	<td class="content">
	The <b>Maximize</b> and <b>Minimize Active View or Editor</b> menu items have been moved to
	the <b>Window > Appearance</b> menu. They used to be in the <b>Window > Navigate</b> menu.
	</td>
	</tr>

	<tr id="terminate-relaunch-history">
	<td class="title">"Terminate and Relaunch" from Run menu, context menu and tool bar</td>
	<td class="content">
	A <b>Terminate and Relaunch</b> option is now available while launching from Run menu, context menu and tool bar.
	The default setting is to launch without terminating previous launches. To enable automatic termination,
	select the option <b>Terminate and Relaunch while launching</b> on
	<b>Preferences > Run/Debug > Launching</b>.

	<p>
	The behavior not selected on the preference page can also be activated on-demand by holding
	the <b>Shift</b> key while launching the configuration from history.
	</p>
	<p><img src="images/launch-preference-terminate-relaunch.png" alt="" /></p>
	</td>
	</tr>

	<tr id="breakpoint-overview-ruler">
	<td class="title">Breakpoints in Overview Ruler</td>
	<td class="content">
	<b>Breakpoints</b> are now visible in the <b>Overview Ruler</b> by default.
	<p><img src="images/breakpoint-overview-ruler.png" alt="" /></p>
	To configure the rendering of annotations, right-click the overview ruler and choose <b>Preferences...</b>.
	This directly opens the preference page <b>General > Editors > Text Editors > Annotations</b>.
	</td>
	</tr>

	<tr>
	<td colspan="2" class="section" id="JDT">JDT</td>
	</tr>

	<tr id="show-junit-failure-trace-in-console-view">
	<td class="title">Show JUnit failure trace in Console view</td>
	<td class="content">
	A new button has been added to the JUnit Failure Trace header to show the stack trace of a failed JUnit test in the Console view.
	The Console view makes it convenient to view a long and wide stack trace, copy parts of the stack trace and navigate to the classes on the stack trace using hyperlinks.
	<p>
	<img src="images/show-junit-failure-trace-in-console-view.png" alt="" />
	</p>
	</td>
	</tr>

	<tr id="skip-button-in-organize-imports-dialog">
	<td class="title">Skip button in Organize Imports dialog</td>
	<td class="content">
	While using the Organize Imports dialog to import multiple unresolved types, you can now skip a type without cancelling the whole operation by using the new Skip button.
	No import statement is added for the skipped type.
	<p>
	<img src="images/skip-button-in-organize-imports-dialog.png" alt="" />
	</p>
	</td>
	</tr>

	<tr id="type-name-with-extension-in-new-java-type-creation-wizards">
	<td class="title">Type name with extension in New Java Type creation wizards</td>
	<td class="content">
	New Java Type creation wizards now accept the <code>.java</code> extension with the type name instead of showing the error message: "Type name must not be qualified".
	For example, to create a new class <code>com.test.C1<T>.java</code>, you can directly paste this qualified type name with extension in the Name field of the New Java Class wizard.
	<p>
	<img src="images/type-name-with-extension.png" alt="" />
	</p>
	</td>
	</tr>

	<tr>
	<td colspan="2" class="section" id="PDE">PDE</td>
	</tr>

	<tr id="first-item-pde">
	<td class="title">New Layout Spy tool</td>
	<td class="content">
	PDE has added a new tool for debugging SWT layouts. To activate it, use the
	shortcut <b>Ctrl+Alt+Shift+F9</b> from any window.
	<p>Usage:</p>
	<ul>
	<li>Click <b>Select Control</b> then click the control you want to inspect</li>
	<li>Enable <b>Show Overlay</b> and navigate the widget hierarchy until you find a
	control whose boundary is correct (the red rectangle) and whose child's boundary
	is incorrect (the yellow rectangle).</li>
	<li>Look at the results of computeSize. If the result of computeSize is correct,
	the problem is in the parent layout or its attributes. Otherwise the problem
	is in the child widget.</li>
	</ul>
	<p>
	<img src="images/layout-spy.png" alt="" />
	</p>
	</td>
	</tr>

	<tr id="pde-changed-exec-env-version-problem">
	<td class="title">Changed Execution Environments creates a version problem</td>
	<td class="content">
	Changing the <b>Execution Environments </b> in a plug-in now creates a problem marker indicating that the minor version should be increased. This happens
	if the minor version is not already increased with respect to the baseline. The preference to control the severity of this problem is located in
	the <b>Version Management</b> tab of the <b>Plug-in Development > API Errors/Warnings</b> preference page.
	<p>
	<img src="images/pde-changed-exec-env-version-problem.png" alt=""/>
	</p>
	</td>
	</tr>

	<tr>
	<td colspan="2" class="section" id="Platform-Dev">Platform Developers</td>
	</tr>

	<tr id="declarative-services-replaceable">
	<td class="title">Declarative services implementation replaceable</td>
	<td class="content">
	In platform bundles, the bundle dependencies to <code>org.eclipse.osgi.services</code> have been replaced with the necessary package imports.
	Mostly <code>org.osgi.service.event</code> needed to be added to the imported packages. This was necessary to avoid a
	uses constraint violation when replacing <code>org.eclipse.equinox.ds</code> with <code>org.apache.felix.scr</code>.
	</td>
	</tr>

	<tr id="swt-1.8">
	<td class="title">SWT requires 1.8 Java runtime</td>
	<td class="content">
	The SWT projects are now compiled at 1.8 compliance level. As a result, a Java runtime of 1.8 or above is required to run SWT applications.
	</td>
	</tr>


	<tr>
	<td colspan="2" class="section" id="Equinox">Equinox</td>
	</tr>

	<tr id="provided-capabilities-metadata">
	<td class="title">Several plug-ins define Provided Capabilities metadata</td>
	<td class="content">
	You can now rely on OSGi's <code>Require-Capability</code> meta data in your Eclipse-based application for
	<code>org.eclipse.equinox.event</code> and <code>org.eclipse.equinox.cm</code> as they now provide
	the corresponding <code>osgi.service</code> capability.
	Additionally, p2 capabilities are specified to be able to configure non-code dependencies that can be interpreted
	by the p2 resolver.
	</td>
	</tr>


	<tr>
	<td colspan="2"/>
	</tr>
	</table>

	<!--
	<p>The above features are just the ones that are new since the previous milestone
	build. Summaries for earlier Oxygen milestone builds:</p>
	<ul>
	<li><a href="https://www.eclipse.org/eclipse/news/4.7/M1/">News for Eclipse Oxygen milestone build M1</a></li>
	</ul>
	-->

	</body>
	</html>