Skip to main content

Platform and Equinox

Views, Dialogs and Wizards

Smart import of directory passed on command-line When a directory name is passed to the Eclipse launcher on command-line (such as eclipse . or eclipse ~/git/eclipse.platform.ui), the generic "smart" Import projects wizard is shown and suggests a plan to import the project into the workspace.

Launch Run and Debug configurations from Quick Access From the Quick Access proposals (usually accessible with Ctrl+3 shortcut) you can now directly launch any of the Run or Debug configuration available in your workspace.

Note: for performance reason, the extra Quick Access entries are only visible if the org.eclipse.debug.ui bundle was already activated by some previous action in the workbench (like editing some launch configuration, or expanding the Run As... menus).

Themes and Styling

Table/Tree background lines shown in dark theme on Mac In dark theme on Mac, the Table and Trees in Eclipse now show the alternating dark lines in the background when setLinesVisible(true) is set. Earlier they had a gray background even if line visibility was true.

Example of a Tree and Table in Eclipse with alternating dark lines in the background:

Tree and Table in Eclipse with alternating dark lines in the background

Improved View Menu Icon The icon used for the view menu has been improved. It is now crisp on high resolution displays and also looks much better in the dark theme.

Compare the old version at the top and the new version at the bottom:

General Updates

Support activating bundles in parallel When the Equinox OSGi Framework is launched the installed bundles are activated according to their configured start-level. The bundles with lower start-levels are activated first. Bundles within the same start-level are activated sequentially from a single thread. A new configuration option has been added (equinox.start.level.thread.count) that enables the framework to start bundles within the same start-level in parallel. The default value is 1 which keeps the previous behavior of activating bundles from a single thread. Setting the value to 0 enables parallel activation using a thread count equal to Runtime.getRuntime().availableProcessors(). Setting the value to a number greater than 1 will use the specified number as the thread count for parallel bundle activation.

The default is 1 because of the risk of possible deadlock when activating bundles in parallel. Extensive testing must be done on the set of bundle installed in the framework before considering enabling this option in a product.

Previous Up Next

Back to the top