| <!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 > Java > Compiler > Errors/Warnings > 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 > Java > Compiler > Errors/Warnings > 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 > Libraries ></b> expand the library <b>> Source attachment > 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 > JDT Plug-in Developer Guide > Programmer's Guide > JDT Core > 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 > General > 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> |
