Eclipse 3.6 - New and Noteworthy
1、Platform and Equinox

Here are descriptions of some of the more interesting or significant changes made to the Eclipse Platform for the 3.6 release of Eclipse. They are grouped into:

    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part1.html#Platform]Platform Changes[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part1.html#Install]Install/Update Changes[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part1.html#Text]Editor Changes[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part1.html#TeamCVS]Team/CVS Changes[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part1.html#Debug]Debug Changes[/URL]

Platform Changes
New platforms  PowerPC 64-bit, Windows 7, and Ubuntu LTS 10.04 have joined the line-up of supported configurations for which SWT and Eclipse are routinely built and tested.
Opening a file from the command line  Based on work in SWT and the native launcher, the Eclipse IDE now supports opening a file from the command line, or opening a file that has been associated with the Eclipse executable. If an instance of Eclipse is already running, that instance will open the file. Otherwise, a new instance will be started.
Resource filters  Projects and folders can now be configured to omit some of their children in the file system from the workspace. The filtered files and directories will not appear in views such as the Project Explorer, and won't be processed by workspace facilities such as builders. Filters can be configured on the Resource Filters page in the Properties dialog. When a filter is added, the following attributes have to be set.

    * Filter type - determines whether only matching resources should be visible (Include) or whether all matching resources should be hidden (Exclude)
    * Applies to - determines the type of resources that should be affected (files, folders, or both)
    * All children (recursive) - indicates that the filter should be used for the entire resource subtree
    * File and Folder Attributes - specifies the filter condition

Dynamic path variables  Linked resources can define their locations relative to user-defined path variables. Now, a set of predefined path variables are available:

    * PROJECT_LOC - pointing out the project location
    * WORKSPACE_LOC - pointing out the workspace location

When these variables are used, they are dynamically resolved based on the context of a linked resource. Those predefined variables may be also used to build user-defined variables.

Virtual folders  Virtual folders are a new type of resource that exist only in the workspace and are not backed by a directory in your file system. These folders can be used to create more flexible project structures by bringing together links to files spread throughout your file system.

Since virtual folders do not exist in the local file system, they can only contain other virtual folders and linked resources.

File system import wizard  The file system import wizard now supports creating virtual folders and linked files and folders.

Linked files and folders can also be created relative to a path variable.
Browser can use WebKitGTK+  Linux users can now use WebKitGTK+ instead of Mozilla as the Browser control's native renderer. See [URL=http://www.eclipse.org/swt/faq.php#browserwebkitgtk]Can the Browser use the WebKit renderer on GTK?[/URL].

UNIX file permissions  The full set of UNIX file permissions are now supported. The attributes can be managed from the Resource Properties page.

New features in Open Resource dialog  The Open Resource dialog supports three new features:

• Path patterns: If the pattern contains a /, the part before the last / is used to match a path in the workspace:

• Relative paths: For example, "./T" matches all files starting with T in the folder of the active editor or selection:

• Closer items on top: If the pattern matches many files with the same name, the files that are closer to the currently edited or selected resource are shown on top of the matching items list.

Progress shown in platform task bar  Progress for long running operations is now shown in the platform task bar on platforms that support this feature. Progress is shown for long running tasks such as workbench startup, install, update, and repository synchronization.

Canceling long-running operations in wizards  There is now a stop button adjacent to the progress bar when a wizard is running a long operation. You can press the stop button (or the Enter or Space key) to cancel the operation being shown in the progress bar.

Quick Access now shows keybindings for commands  Quick Access (Ctrl+3) now shows keybindings for commands so you can save yourself from all that typing and just use the keyboard shortcut the next time you need to run a command.

Search keywords in wizards  The File > New, File > Import..., and File > Export... wizards now support searching by keyword. You can type a search term that doesn't appear in the wizard name, and the term will match against search keywords registered for that wizard. For example if you search for "zip" or "directory" in the import wizard, you will be shown the wizards for importing from archives or the file system, respectively.

Local History pruning can be disabled  The local history size constraints can now be disabled. Users that never want to discard history no longer need to wait on shutdown for history cleanup to occur. To disable history cleaning, go to Preferences > General > Workspace > Local History and disable Limit history size. Note that when this option is chosen, disk usage for the workspace local history will continue to grow indefinitely.

Hide empty fast view bars  In order to clean up the UI and gain some space in the trim area, there is a new preference on the General > Perspectives page that allows you to hide the Fast View Bar when it's empty. Note that this option does not inhibit the functionality; if there are fast views in the perspective (or you make a view a fast view) the bar will be shown regardless of the preference setting.

Edit linked resource location  Linked resource locations can now be changed by selecting the Edit... button in the Resource Properties page.

File and folder operation dialog  When dragging files and folders from the operating system shell (such as Windows Explorer) onto Project Explorer, a dialog appears to let you choose how the files should be imported.

The dialog allows you to simply copy files and folders (the traditional operation) but also easily create linked resources and virtual folders hierarchies in a project folder by simply drag and dropping files and folders.

The dialog also creates project path variable relative linked resources automatically, so that projects remains portable while using linked resources.
Install/Update Changes
Grouping by license in install wizard  Software to install is now grouped by license in the Review Licenses page of the install wizard. This means you no longer need to select each item being installed to ensure all applicable licenses have been reviewed.

NTLMv2 proxy support  Support has been added to the platform for communicating with NT Lan Manager proxies (NTLMv2). You can now install and update software in the Eclipse user interface when running behind proxies that use this protocol.
Comparing configurations in the Installation History  The Installation History page now allows you to compare two different installation history configurations. Now you can more easily see what was installed, uninstalled, or updated in the various installation configurations. You can also delete unwanted installation configurations in order to reduce clutter and free up disk space.

Editor Changes

These changes apply to all textual editors in the SDK.
Resize content assist and hover pop-ups under Linux  Content assist and most hover pop-ups are now resizable in textual editors under Linux/GTK.

All folded annotations are now visible in the rulers  Until now, only errors and warnings were shown in the vertical and overview ruler when code is folded. As of this release, all annotations from the folded region are visible:

Show ruler annotation tooltip command  The annotation tooltip that appears when you hover over an icon in the vertical ruler on the left of a textual editor can now also be shown by pressing a key sequence. However, out of the box no key sequence is defined for that. Go to the General > Keys preference page to assign a key sequence to the Show Ruler Annotation Tooltip command.

Better handling of unmappable characters on save  There is now better support for characters that cannot be saved with the current encoding:

Print dialog remembers user selected options  The Print dialog now remembers the following user selected options for all textual editors until the workbench is shutdown:

    * Selected printer
    * Print to file
    * Printer preferences: These are printer specific options like paper size, page order orientation etc.

Team/CVS Changes
Enhanced Open in Compare editor menu  The context menu of the Compare editor contains Open and Open With actions, which open the file in full-fledged editors. Now, these actions set the selection and the caret position in the newly opened editor based on the selection in Compare Editor.

Apply patch in Synchronize view  The Synchronize view now allows to synchronize with a patch either by pasting the patch into the view or by using the Synchronize wizard. If you prefer this new way of applying patches, you can replace the modal Apply Patch dialog with the Synchronize view by selecting the new Apply patch in Synchronize view option on the Team preference page:

When synchronizing with a patch the drop-down menu in the Synchronize view offers patch options including Reverse, Fuzz Factor..., Generate .rej File and Ignore Leading Path Segments....

Moreover the Synchronize with Patch wizard displays a page with inaccessible projects referred from within the patch. Projects selected on this page will be opened prior to synchronization.

"Link with Editor" in Synchronize view  The Synchronize view can now be linked with the active editor. Moreover, the view is now one of the 'Show In' targets when in the Synchronize perspective.

Logical models in Commit wizard  The Commit wizard now shows logical models just like the Synchronize view does.

Sorted diffs in patches  The Create Patch action now creates patches that contain changes sorted by project and file path. This makes comparing patches much easier.
Usability enhancement to Configure Branches and Versions  Now the Configure Branches and Versions action in the repository view is enabled for multiple selections. This means that you are able to choose any file in the selection as a tag source for all selected folders.

Warning about possible inaccuracy in comparison result  The compare framework caps the result accuracy for large files. This used to happen silently, which confused users. Now when the faster algorithm is used a warning label appears.

Debug Changes
Columns in Expressions view  The Expressions view now supports column display just like the Variables view. To switch to a column presentation select Layout > Show Columns from the view's menu.

Users can also quickly edit existing expressions in-line by clicking on the expression in the Name column. To add a new expression, click on the Add new expression place-holder at the bottom of the list.
Breakpoint detail panes  The breakpoints view now provides detail panes to display and edit breakpoint properties. Use the view's Layout menu to configure the orientation of the detail pane or hide it.

For example, the detail pane for a Java line breakpoint allows its condition to be edited in place with content assist. Use the File > Save (Ctrl-S) action to save a condition that has been edited. Check box and radio button properties are saved immediately.

2、Java development tools

Here are descriptions of some of the more interesting or significant changes made to the Java development tools for the 3.6 release of Eclipse. They are grouped into:

    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part2.html#JavaEditor]Java Editor[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part2.html#JavaFormatter]Java Formatter[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part2.html#JavaRefactoring]Java Refactorings[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part2.html#JavaCompiler]Java Compiler[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part2.html#JavaViews]Java Views and Dialogs[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part2.html#JUnit]JUnit[/URL]

Java Editor
Fix multiple problems via problem hover  The problem hover now shows quick fix links that fix multiple instances of a problem in a file:

The new links behave the same as pressing Ctrl+Enter in the Quick Fix proposal list (Ctrl+1).
Javadoc hovers include annotations  Javadoc hovers now include annotations:

Javadoc hovers render {@value}  Javadoc hovers now render {@value} inlined:

Command to open an implementation  The Open Implementation command is available from the Navigate menu. A key binding can be assigned on the General > Keys preference page.

This action is enabled on text selections in the Java editor for overridable methods and directly opens the implementation in case there's only one, or shows all the concrete implementations for that method in the hierarchy of its declaring type, using the Quick Type Hierarchy.
Improved content assist for getter and setter proposals  Content assist now proposes all possible getter and setter proposals in case of field name clashes and no longer proposes setter proposals for final fields.
New 'Java Code Style Preferences' category when importing or exporting preferences  When importing or exporting preferences, a new category is available that allows you to control whether Java code style preferences are imported or exported:

Java Formatter
Control the formatting in code sections  This preference allows you to define one tag to disable and one tag to enable the formatter (see the Off/On Tags tab in your formatter profile):

Here is an example of formatted code which is using code sections with the tags defined as shown above:

New strategy to wrap nested method calls  The Java formatter now tries to wrap the outermost method calls first to have a better output when wrapping nested method calls.

Here is an example of a formatted code where the formatter has wrapped the line earlier, e.g. between the arguments of the outermost message call. Doing this, each nested method call is kept on a single line:

A new preference allows you to disable this new strategy, e.g. if you want to format your code as before:

Note: Currently the new strategy only applies to nested method calls, but that might be extended to other nested expressions in future versions.
Insert a new line after a label  

For example, with this preference activated as shown above, the loop will be placed on a new line after its label:

Align element-value pairs in annotations  

For example, the two annotation arguments are each put on a new line if the chosen alignment policy for this preference is Wrap all elements, every element on a new line and if the Force split check-box is selected:

Wrap method declaration  

For example, the modifier, the return type and the name of the method can each be placed on a new line if the chosen alignment policy for this preference is Wrap all elements, every element on a new line and if the Force split check-box is selected:

Put start and end of comments on separate lines  This preference lets you to decide whether the beginning and the ending characters of a multi-line comment will be placed on separate lines or not:

For example with the above preferences disabled, a block comment can be formatted to take less lines in the code:

Skip formatting of line comments starting at first column  This preference lets you decide whether line comments which start at the first column of the file will be formatted or not:

For example, with this preference not activated as shown above, the first comment is untouched after the formatting:

Java Refactorings
Extract Method improvements  The Extract Method refactoring now handles selections that contain continue statements. To preserve the semantics of the existing code, the selection needs to include the last statement of the loop. In the extracted method, continue statements are changed to return:

For a selection that would need multiple return values in the extracted method, Eclipse now lists the conflicting variables in the error message:

Move type to new file refactoring  The Convert Member Type to Top Level refactoring has been renamed to Move Type to New File and now allows any secondary type in a file to be moved into its own file. The action continues to work for member types.

Java Compiler
Report missing @Override for method implementations in 1.6 mode  The compiler now reports about missing @Override annotation in the case where a method implements a method from an interface:

This new behavior can be controlled via Java > Compiler > Errors/Warnings in the Annotations section and configured for Clean Up and Save Actions.

Note: This is reported only in 1.6 mode as @Override annotations are not expected on a method implementation in 1.5.
New "rawtypes" token for @SuppressWarnings annotation  The compiler now makes the distinction between warnings reported for raw type usage versus warnings reported for unchecked generic operations.

In case it is not possible to update the code with the new token, the suppressRawWhenUnchecked=true system property can be set when starting Eclipse.
@SuppressWarnings for optional errors  The @SuppressWarnings annotation can now also suppress optional compile errors:

In this example, Local variable is never read has been set to Error.

This behavior can be enabled on the Java > Compiler > Errors/Warnings preference page in the Annotations section with the check box Suppress optional errors with '@SuppressWarnings'.
Compiler detects unused object allocation  The Java compiler can now detect unused object allocations:

This detection is disabled by default and can be enabled on the Java > Compiler > Errors/Warnings preference page at the end of the Potential programming problems section.
Import and export compiler preferences  The new 'Java Compiler Preferences' category allows to just import or export the compiler preferences:

Java Views and Dialogs
New build path error decorator  Build path problems are sometimes easy to miss among other problems in a project. The Package Explorer and Project Explorer views now show a new decorator on Java projects and working sets that contain build path errors:

The concrete errors can be seen in the Problems view, and if you open the view menu and select Group By > Java Problem Type, they all show up in the Build Path category:

Package name abbreviations  Package names in Java views can now be abbreviated with custom rules. For example, the following rules produce the rendering shown below:

org.eclipse.ui={UI}
org.eclipse.ui.texteditor={T}
org.eclipse.ui.internal.texteditor=[iT]

Without abbreviations:  With abbreviations:
 

The abbreviation rules can be configured on the Java > Appearance preference page.
Remove nodes from Call Hierarchy  The Call Hierarchy now allows to remove a single or multiple nodes from the view via context menu:

Improved refresh in the Call Hierarchy  The Call Hierarchy now allows to refresh single or multiple elements at once via the Refresh (F5) action from the context menu:

This will refresh the selected elements and their direct children. The action in the toolbar has been renamed to Refresh View and still refreshes the entire view.
Type Hierarchy computed in background  The Type Hierarchy is now computed in an operation that can be sent to the background (or always runs in the background, depending on your settings):

Your workbench is no longer blocked while a big hierarchy is computed.
Export all profiles  The Formatter preference page and the Clean Up preference page now have an Export All... button that allows exporting all user-defined profiles into an XML file. The exported profiles can be imported from the XML file at once using the Import... button.

Opening attached Javadoc now uses preferred web browser  Open External Javadoc has been renamed to Open Attached Javadoc and now uses the configured web browser:

Instance counts  The Variables view provides a new column displaying the number of instances corresponding to the concrete type of each variable. To display the column, select Layout > Select Columns... from the view's menu, and then select Instance Count from the Select Columns dialog. Note that instance counts are only available debugging on JavaSE-1.6 (or newer) and are not applicable to primitive types.

You can also display the instance count of a selected type in an editor or editor outline and selecting Instance Count... from the context menu. The result is displayed in a dialog.
Java breakpoint detail  The Java breakpoint detail panes now display all properties in a single pane. Detail pane orientation can be configured via the Layout view menu.

For example, a Java line breakpoint allows its condition to be edited in place with content assist. Use the File > Save (Ctrl+S) action to save a condition that has been edited. Radio button properties are saved immediately.
Source attachments for referenced JARs  Source attachments can now be configured separately for JARs that are not directly on the classpath of a Java project, but referenced from another JAR via the Class-Path: attribute in the MANIFEST.MF:

Find broken externalized strings improvements  Source > Find Broken Externalized Strings now reports less false positives:

• It ignores all methods that don't take a single parameter of type String. For example, method calls like Messages.getResourceBundle() are no longer listed as undefined keys.

• Constants used for message keys are now correctly recognized. In the example below, MAIN_INDIRECT is no longer listed as an undefined key:

New Java appearance category when importing or exporting preferences  There is a new category available when importing or exporting preferences that allows you to control whether Java > Appearance preferences are imported or exported:

JUnit
JUnit 4.8.1  The JUnit 4 version shipped with Eclipse has been updated to 4.8.1.
2 versions of org.junit plug-in  The SDK now ships 2 org.junit plug-ins (versions 3.8.2 and 4.8.1). Clients that want to run JUnit Plug-in Tests with a Java 5 or later VM and that require org.junit with a version bound that does not include 4.x need to update their version bound to include 4.x (e.g. by specifying Require-Bundle: org.junit;bundle-version="3.8.2". If they don't update their bounds, both versions of org.junit are resolved at run time, which leads to errors when test classes are loaded.

For complete details on the steps required to transition to using JUnit4 or to continue using JUnit3, please see:
[URL=http://wiki.eclipse.org/Eclipse/Testing/JUnit4_Changes]http://wiki.eclipse.org/Eclipse/Testing/JUnit4_Changes[/URL].
JUnit view opens test result URL  The JUnit view can now directly load test result files from an URL. You can either just drag and drop an URL to the view or open the Test Run History... tool bar button's drop-down and choose Import from URL... to enter an URL from which the test results should be loaded.

Supported test run formats are XML files exported from the JUnit view or generated by the Ant JUnit task.
JUnit imports test results with <skipped> nodes  The JUnit view can now import test run files that contain <skipped> nodes. Eclipse and the Ant JUnit task do not generate such nodes, but e.g. test result files from Apache Maven do generate them for ignored JUnit4 tests.
Edit test method in JUnit launch configuration  In JUnit launch configurations, you can now edit the test method:

When the test method is empty, all tests in the class will be run.
org.eclipse.jdt.junit split  The non-UI parts of the org.eclipse.jdt.junit plug-in have been split off into the new plug-in called org.eclipse.jdt.junit.core. This change does not affect existing clients of the org.eclipse.jdt.junit plug-in, but allows new clients to use only the launcher without requiring all the UI dependencies.

Here are descriptions of some of the changes of interest to plug-in developers made to the Eclipse [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part3.html#Platform]Platform[/URL], [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part3.html#Equinox]Equinox[/URL] and [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part3.html#SWT]SWT[/URL] for the 3.6 release of Eclipse.
Platform Changes
Platform test framework support for JUnit 4  The platform's automated testing framework now supports running tests with JUnit 4. The test framework previously only allowed running with JUnit version 3.
Headless external tool builders  Launching support for Ant and external tools is provided by the new headless plug-ins org.eclipse.ant.launching and org.eclipse.core.externaltools. This allows applications without a user interface to leverage the launch support programmatically and it allows projects configured with external tool builders to be built in headless environments.
Event admin added  The OSGi event admin specification provides a general purpose event bus for posting and sending events to event handlers. The Equinox event admin implementation has been added to the platform feature.
Help UI extensibility  New extension points allow additional buttons and frames to be added to the help web application. In the image below the title search frame, the rightmost button and the frame below the content page are all contributed.

Customizable help footer  

The customization org.eclipse.help.base/footer allows a footer to be added to the Eclipse help system. This can be used for infocenters or in Eclipse-based products.

.
Scoping by criteria in help system  The help web application now allows the table of contents, the index and the search results to be filtered by book/topic or by criteria. Criteria are defined in the table of contents or using the extension point org.eclipse.help.criteriaDefinition. The list of displayed criteria is defined at the product level. Products which do not define criteria (including the Eclipse SDK) will not show any UI for criteria.

Sorting help topics  A new attribute "sort" has been added to the <toc> and <topic> elements in a table of contents which causes subtopics to be sorted alphabetically when the value is set to "true".
Reusable intro news reader  The EclipseRSSViewer class allows multiple RSS news readers to be easily added to an intro page.

See entries in keyword index  See entries can now be added to the help system keyword index.

Extension point for help search  A new extension point org.eclipse.help.base.searchParticipant has been added. This allows clients to add documents not in the html or xhtml format to the search index used by the help system. This should be used in place of the deprecated extension point org.eclipse.help.base.luceneSearchParticipants which is not binary compatible across Lucene versions.
Equinox Changes
Multi-locale support in extension registry  The Equinox extension registry now supports running in a multi-locale mode. When running in this mode, translated extension attributes can be obtained for any locale, whereas they were previously only available for the system's current locale. Multi-locale mode is enabled via the -registryMultiLanguage command line argument, or by setting the Java system property eclipse.registry.MultiLanguage=true.

The registry also uses a new LocaleProvider service for obtaining the locale for a given execution context. This allows a system to provide an alternative mechanism for computing the current locale, rather than using the singleton locale defined by the Java runtime environment.
New Equinox weaving feature  The byte code weaving work in the Equinox incubator has passed the graduation review and the major parts of the work are now part of the Equinox distribution.

Equinox Weaving provides a general infrastructure for load-time byte code weaving for the Equinox OSGi runtime. Currently Equinox Weaving includes a weaver for AspectJ to load-time weave aspects into bundles (AspectJ Development Tools and the Scala IDE for Eclipse already use this to realize deeper integration with the Eclipse Java development tools, for example).

These four bundles are contained in the distribution:

    * org.eclipse.equinox.weaving.hook: The framework extension project containing the hooks to insert byte code weaving and caching at load-time.
    * org.eclipse.equinox.weaving.aspectj: Contains the bridge to use AspectJ as load-time weaving implementation.
    * org.eclipse.equinox.weaving.caching: Provides caching for woven byte code for standard Java virtual machines.
    * org.eclipse.equinox.weaving.caching.j9: Contains an alternative cache implementation that uses IBM J9 VM shared classes for caching woven classes.

Multi-session Equinox console  The Equinox console has been enhanced to allow multiple console sessions to be connected. Previous versions of the Equinox console would only allow a single session to be connected at a time. The console only allowed for connections from two built connection types, through standard in/out or though a telnet port.

A new service interface has been introduced: org.eclipse.osgi.framework.console.ConsoleSession. Implementers of a console session register themselves as an OSGi service. The console implementation will then automatically use the console session for input and output of a console connection.
Revert support in p2 director  The p2 director application now supports reverting to an earlier profile state from the command line. Use the new -revert argument to specify a previous profile state to revert to.
SWT Changes
Browser can use WebKitGTK+  Linux users can now use WebKitGTK+ instead of Mozilla as the Browser control's native renderer. See [URL=http://www.eclipse.org/swt/faq.php#browserwebkitgtk]Can the Browser use the WebKit renderer on GTK?[/URL].

Icon support for GTK Text widgets  The text widget can now display the search and cancel icons inside the widget. This runs on Linux platforms with a GTK version of 2.16 or greater.

Mozilla browser support on Solaris SPARC  Mozilla browser support has been added for the Solaris SPARC platform (Solaris 10, GTK+).
Browser closing API  The new API method Browser.close() is used to close a browser, but allows the close to be cancelled by an onbeforeunload handler. See [URL=http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet326.java]Snippet 326[/URL].

Key events for F16-F20  New key event constants have been added for the keyboard function keys F16 to F20.
DND insertion feedback for tables  The default drop target effect for Table now supports DND.FEEDBACK_INSERT_BEFORE and DND.FEEDBACK_INSERT_AFTER.

Horizontal mouse wheel  New event constants have been added for horizontal mouse wheels. See SWT.MouseHorizontalWheel and SWT.MouseVerticalWheel.
Variable tab stops in StyledText  New API in StyledText allows the application to specify a non-uniform sequence of tab stops. See [URL=http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet325.java]Snippet 325[/URL].

StyledText: per line variable tab stops  Tab stop support in StyledText has been improved to allow each line to have its own sequence of tab stops. [URL=http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet328.java]Snippet 328[/URL] has been modified from Snippet325 to show this.

CLabel set/get margins  New API has been added to CLabel to set and get the left, top, right and bottom margin spacing.
Key location  A new field has been added to KeyEvent to allow the application to identify which keyboard key originated the event, for example, right or left shift key. See KeyEvent.keyLocation for details.
New API in Scrollbar  New methods have been added to Scrollbar to return the bounds for the thumb and its track. See ScrollBar.getThumbBounds() and ScrollBar.getThumbTrackBounds().
State mask for selection events  SelectionEvent.stateMask is now set on selection and default selection events for all native controls.
Orientation event  A new event has been added to Text, Combo, and StyledText. It is sent when the writing direction is changed via keyboard shortcut. See SWT.OrientationChanged
Browser.setUrl() can specify post data and headers  The new API Browser.setUrl(String url, String postData, String[] headers) allows clients to include post data and add/override header values when initiating HTTP requests. See [URL=http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet330.java]Snippet 330[/URL] for an example.
Wrap indent in StyledText  StyledText and TextLayout now offer API to allow the application to control the amount of indent space for wrapped lines. See [URL=http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet331.java]Snippet 331[/URL].

Improved bidi segments support  The bidi segments support in StyledText and TextLayout was changed to allow the application to specify which Unicode Control Characters to use in the segments boundaries. See [URL=http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet332.java]Snippet 332[/URL].

Right-to-Left text support on Cocoa  On Cocoa, setting the SWT.RIGHT_TO_LEFT flag changes the default text reading direction to right to left.

Skin engine support  New API added to allow CSS engines to skin widgets at the appropriate time (See SWT.Skin and Widget.reskin(int)). For more info see [URL=http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet333.java]Snippet 333[/URL].
New layout API  New API added to Composite to support automatic deferred layout. See Composite.layout(Control[], int).
Browser.setText() can restrict content permissions  New Browser API setText(String html, boolean trusted) allows clients to restrict the permissions that are given to Browser content that is set from a String. Restricting permissions is suggested when the source of the content is not trusted.
Accessibility upgrade  SWT Accessibility has new API for making applications more accessible to Assistive Technology products such as screen readers. The new API can be found in the org.eclipse.swt.accessibility package. For examples, see the org.eclipse.swt.examples.accessibility package, and the [URL=http://www.eclipse.org/swt/snippets/#accessibility]Accessibility snippets[/URL].
SWT.OpenDoc Event  A new event type has been added to SWT to notify applications that a document should be opened. Listeners for OpenDoc events can be added to a Display.

Support has also been added to the Equinox launcher, and the Eclipse workbench. Users are now able to associate file types with Eclipse and have Eclipse launched when they open a file of an associated type.
Program working directory  New API has been added to Program to allow the working directory to be specified when launching an executable. See Program.launch(String fileName, String workingDir) for more details.
XULRunner 1.9.2 support  The Browser widget now has full support for the recent release of XULRunner 1.9.2.
TaskItem overlay image  The new API TaskItem#setOverlayImage(Image) allows clients to set an image to be displayed on top of the application button in the taskbar. See [URL=http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet336.java]Snippet 336[/URL] for an example.

TaskItem overlay text  The new API TaskItem#setOverlayText(String) allows clients to set a short text to be displayed on top of the application button in the taskbar. See [URL=http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet336.java]Snippet 336[/URL] for an example.

TaskItem progress  The new APIs TaskItem#setProgress(int) and TaskItem#setProgressState(int) allows clients to show progress indication in the application button in the taskbar. See [URL=http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet336.java]Snippet 336[/URL] for an example.

TaskItem menu  The new API TaskItem#setMenu(Menu) allows clients to specify a menu for the application button in the taskbar. Running on Windows 7:

Running on Mac OS X:

CTabFolder renderer  CTabFolder has been improved and now allows clients to change its look by implementing their own renderers.

Custom traversals  New API Control.traverse(int, event) enables clients to request that a customized traversal be performed. For an example of this see [URL=http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet338.java]Snippet 338[/URL].
Draw background at an offset  New API was added in Composite.drawBackground that allows for drawing of a parent background at an offset specified by the child. This is useful for aligning patterns between the parent and child when dealing with non-rectangular shapes.

[URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part2.html]Previous[/URL]     [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part4.html]Next[/URL]

4、Plug-in Development Environment

Here are descriptions of some of the more interesting or significant changes made to the Plug-in Development Environment (PDE) for the 3.6 release of Eclipse, grouped into:

    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part4.html#ViewsAndEditors]Views and Editors[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part4.html#Launching]Launching[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part4.html#TargetPlatform]Target Platform [/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part4.html#Export]Import and Export[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part4.html#APITooling]API Tooling[/URL]
    * [URL=http://download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080911/eclipse-news-part4.html#Build]Build[/URL]

Views and Editors
OSGi console  An OSGi console is now available to interact with the running framework. Use the Open Console drop down action in the Console View to open a Host OSGi Console.

You can then enter OSGi commands into the console to interact directly with the framework running the IDE.
XML error reporting in context help and table of contents editors  The context help editor and table of contents editor now report XML errors.

Spell checking in context help and table of contents editors  

Spell checking is now available in the Table of Contents (TOC) and Context Help editors.

Configurable problem severities for build.properties  Severities for problems in build.properties can now be configured individually via the Preferences > Plug-in Development > Compilers preference page. Problem severities can also be configured at the project level via a project's Properties > Plug-in Development > Plug-in Manifest Compiler property page.

Search repositories quickfix  A new quickfix allows you to conveniently search a set of repositories for a missing imported package and have a bundle supplying the package added to your target platform.

API for plug-in project creation  An API is now available to create and modify plug-in (bundle) projects. The API provides a description of a project's bundle related attributes and allows them to be modified declaratively. For example, a bundle's activator, required bundles, package exports and imports can be queried and defined. As well, the root of bundle (i.e. the folder containing META-INF/MANIFEST.MF) can be placed anywhere inside a project (rather than just the root project folder). The new API is available in the org.eclipse.pde.core.project package of the org.eclipse.pde.core bundle.
Launching
Feature based launch  You can now manage the set of plug-ins launched in Eclipse Applications, JUnit Plug-in Tests, and OSGi Framework launch configurations by selecting a set of features.

Features from both the workspace and the target can be included. Individual plug-ins can be added to the launch to include plug-ins that are not part of a feature. PDE will launch all the selected plug-ins as well as all required plug-ins.

Features in the workspace are used over external features, however, this can be configured by un-checking 'Use features from workspace if available'. Bundles in the workspace are used over external bundles in the target platform. However, this can be configured by modifying the configuration's default bundle resolution policy, or can be configured per feature using the cell editors in the 'Plug-in Location' column.
Headless launching support  Launching support for Eclipse Applications, JUnit Plug-in Tests, and OSGi Frameworks is provided by a new headless plug-in (org.eclipse.pde.launching). This allows applications without a user interface to leverage the launch support programmatically.
Console log  By popular demand, -consoleLog is added to new launch configuration program arguments by default.

Support software installation while running and debugging  Launched Eclipse Applications can now support software installation operations. When the new option is checked (on the Configuration tab of Eclipse Applications), a p2 profile is generated when running or debugging. The profile initially contains all bundles in the target and can be modified by software installation operations. The profile is regenerated on each subsequent run or debug session, but is maintained across restart operations.

Import and Export
Import from CVS  The Plug-in Import wizard allows you to import projects from CVS corresponding to bundles in the target platform. This feature is available for bundles that define the Eclipse-SourceReferences header. On the first page of the import wizard select the Import As > Projects from a repository option.

The second page allows you to choose from all bundles with source repository information. Select the bundles you want to import and press Next.

The last page of the wizard allows you to import the specific versions of the bundles used in the target platform or from HEAD. Pressing Finish will import the projects into your workspace.

You can also import projects from the Plug-ins view. Use the Import As > Project from a Repository... action to import plug-ins from CVS.

Export target content  It's now possible to export the contents of your current target platform into a destination directory via the export active target definition wizard. In the list of export wizards (File -> Export...), you'll find the wizard available under Plug-in Development -> Target definition.

Note: This will copy all features and plug-ins that are part of your currently set target platform to the destination directory.
Target Platform
Feature based target  You can now manage the set of bundles in a target platform by selecting a set of features. Additionally, you can select from bundles that are not contained in any feature. On a target definition's Content tab select the Manage using Features radio button. This provides coarse grained management of bundles in a target. When a feature is selected, all bundles in that feature are added to the target.

Add to target platform dialog  The Add Artifact to Target Platform dialog (Ctrl+Shift+Alt+A) allows you to quickly search a set of repositories for dependencies (bundle, feature or package) to add to your current target platform.

Synchronize Java search with target platform  You can automatically synchronize Java search operations with the target platform via the Preferences > Plug-in Development preference page.

Java search operations are scoped to workspace projects and their dependencies. Developers don't typically have the entire target platform in their workspace and thus Java search operations don't locate references from many upstream plug-ins. You can manually add plug-ins to the Java search path using the Add All Plug-ins to Java Search action in the Plug-ins view. However, the new preference automatically keeps the search path in synch with the target platform.

Under the covers a project named External Plug-in Libraries is created with all external plug-ins in the target platform on its build path.
API Tooling
Compare with baseline now reports deprecations  When performing Compare With > API Baseline..., deprecation changes are now reported. This allows you to quickly identify what has been deprecated between two releases of a project.

API use reports  

You can generate reports describing what API and internals are being used by other bundles. API use reports have been integrated as an external tool (Run > External Tools > External Tool Configurations...). For example, the following report settings are used to generate a report revealing which internal components of the debug platform are being consumed by JDT.

A report is run against a set of bundles which can be specified as an API baseline, a target definition or a directory of bundles. You can search for API and/or internal references and you can limit the report to specific bundles by using regular expressions. You must specify an output location (directory) for the report and whether to generate HTML.

Package exports in bundle manifests are used to determine package visibility. Any package exports with an x-internal or x-friends modifier will be considered internal. All other packages are considered API. The Patterns tab can be used to augment package visibility information by specifying regular expressions to identify packages, and whether those packages should be considered API or internal. For example, since TPTP specifies all packages as API, the following patterns could be used to identify its internal packages.

Customize API use scan reports  A new wizard helps you customize API use reports. From the Patterns tab of an API Use Report launch configuration (available via External Tools), press the Add button to open the wizard and create custom pattern filters.

An Archive Pattern allows specific jars within bundles to be omitted from the scan. A Package Pattern allows you to specify which packages should be considered API or non-API (override visibility definitions in bundle manifests). A Report Conversion Pattern allows specific references to be filtered from the final report. You can filter references from or to locations based on regular expressions.
Enhanced build.properties validation  Redundant entries in source builds are now flagged with a warning by default.

API use report filters  You can now add filter patterns to API use reports to constrain what references are reported. This feature is available in UI and in API tooling Ant tasks. When you press Add on the Patterns tab a wizard allows you to craft a variety of patterns. An archive pattern is used to skip specific jars. A package pattern is used to define a package as API or internal (to override a bundle manifest). A report conversion pattern is used to skip specific references during report creation (by specifying a regular expression of reference origins to skip).

For example, to use an archive pattern to filter references from specific archives within bundles, select Archive Pattern and press Next. The wizard allows you to easily craft an archive pattern.

When you press Finish the pattern appears in the Patterns table.

API use report details  You can now provide comments to accompany an API use report, which will show up in the reports as additional information along with the scan parameters for reference. This feature is available in the UI and in API tooling Ant tasks.

The resulting report could look like the following.

Build
Enhanced compiler error options for PDE build  PDE/Build can now take advantage of new support from the JDT compiler to specify that certain warnings should instead be reported as errors.

Set the property javacErrors.<library> in your build.properties. Similar to the javacWarnings.<library> property, specify the [URL=http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm]warnings[/URL] that should be reported as errors:

     javacErrors.. = forbidden,discouraged,
     javacErrors.library.jar = deprecation,nullDereference
     

Synchronize project settings with PDE build  To ensure PDE will export and build your project with the same settings as in the workspace there are new checks to synchronize project specific compiler and build path settings with build.properties. The following validations are performed and quick fixes are provided for any problems.

    * Compiler compliance, source and target levels match jre.compliance.profile, javacSource, and javacTarget properties (only required when compiler settings do not match default settings for a bundle's required execution environment).
    * Folders in source.<library> exist, are source folders on the Java build path, and are not duplicated.
    * Folders in output.<library> exist, are output folders or class file folders on the Java build path, and are not duplicated.
    * Each output.<library> entry contains all output locations of its corresponding source folders on the Java build path.
    * Source folders targeted to different libraries do not share the same output location.
    * Source folders are not included in src.includes entries (they are included by default).
    * Additionally, a check can be performed to ensure an output.<library> exists for each source.<library> entry. By default, this problem is ignored but can be turned on via Preferences > Plug-in Development > Compilers (or project specific Properties > Plug-in Development > Plug-in Manifest Compiler). This option is useful when using the PDE option to export existing class files from the workspace.

Synchronize project settings with PDE build  It's easier to synchronize your project specific compiler settings and file encoding settings with PDE build. Two new options appear in the Build section of the Preferences > Plug-in Development > Compilers preference page. By default the new options are set to Ignore.

When set to Warning or Error problem markers will appear when your project settings are not reflected in build.properties. Quick fixes are available to help you synchronize the settings.

A new javacProjectSettings property is supported in build.properties. The value can be a project relative path to a preference settings file of compiler options supported by the JDT compiler, or it can simply by true to indicate the default preference file should be used (.settings/org.eclipse.jdt.core.prefs).
Plug-in specific compiler arguments  A bundle can now specify custom compiler arguments to be used in export or releng builds by setting compilerArgs in its build.properties file..

These arguments will be specified in addition to whatever general compiler arguments are specified by the releng setup.
Custom compiler adapters  A bundle can now specify a custom ant compiler adapter to be used during export or releng builds. This allows for compiling non-java sources such as AspectJ or Groovy provided a suitable adapter is available.

Set compilerAdapter in the bundle's build.properties file. As well, set sourceFileExtensions to a list of file extensions which should be treated as source and automatically copied to generated source bundles.
Improved error reporting from PDE build  A new prereqErrors.log file is generated by PDE build. The file helps locate bundles lowest on the stack with compilation errors. An entry is added for each bundle with build errors describing any prerequisite bundles that contained compile errors. Entries are added in the order bundles are compiled. For example:

org.eclipse.debug.ui_3.6.0.201004141459: the following prerequisites contain compile errors
    org.eclipse.debug.core_3.6.0.201004141459

The End