Skip to content

Commit

Permalink
N&N for 4.24 (#32)
Browse files Browse the repository at this point in the history 
fixes #21

Review and fix news content
  • Loading branch information
@lshanmug
lshanmug committed May 25, 2022
1 parent da68d47 commit db9824c
Show file tree
Hide file tree
Showing 5 changed files with 43 additions and 47 deletions.
2 changes: 0 additions & 2 deletions 4.24/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,9 @@ <h1>Eclipse 4.24 - New and Noteworthy</h1>
The Eclipse installer and other packages can be downloaded from the <a href="https://www.eclipse.org/downloads/packages/installer">Eclipse Installer</a> page.
</p>

<!--
<p>
The 4.24 release notes for the Eclipse SDK project can be found <a href="https://www.eclipse.org/eclipse/development/readme_eclipse_4.24.php">here</a>.
</p>
-->

<p>Here are some of the more noteworthy items available in this release.</p>

Expand Down
30 changes: 15 additions & 15 deletions 4.24/jdt.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -74,9 +74,9 @@ <h2>JUnit</h2>
</td>
</tr>
<tr id="junit5-rerun-failures-first"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=578747 -->
<td class="title"><a href="#junit5-rerun-failures-first">JUnit5 rerun failures first support</a></td>
<td class="title"><a href="#junit5-rerun-failures-first">JUnit 5 'Rerun failures first' support</a></td>
<td class="content">
Support for rerunning a test with failures first from the <b>JUnit View</b> is now supported for JUnit5 tests. This support already existed for JUnit4 tests but was previously disabled for JUnit5 testing.
Support for rerunning a test with failures first from the <b>JUnit View</b> is now supported for JUnit 5 tests. This support already existed for JUnit4 tests but was previously disabled for JUnit5 testing.
<p>
To run, click on the <b>Rerun Test - Failures First</b> button in the JUnit view.</p>
<p><img src="images/run-failures-first-before.png" alt="Before"/></p>
Expand All @@ -98,18 +98,18 @@ <h2>Java Editor </h2>
<tr id="strconcat-to-textblock"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=561484 -->
<td class="title"><a href="#strconcat-to-textblock">Remove unused private method parameters</a></td>
<td class="content">
A new cleanup and quick-assist has been added to remove unused parameters of private methods. If removing parameters might
A new <b>cleanup</b> and <b>quick-assist</b> has been added to remove unused parameters of private methods. If removing parameters might
lead to a conflict with an another method, the private method is renamed to be unique. The cleanup is not available if there
is a method reference to the method, as in <code>stream.filter(MyClass::foo)</code>
<p>
To apply the cleanup, select the <b>Remove unused private method parameters</b> checkbox on the <b>Unnecessary Code</b> tab in your cleanup profile:</p>
<p><img src="images/remove_param_1.png" alt="Preference"/></p>
<p>
With the cleanup, the following:
With the cleanup, the following code:
</p>
<p><img src="images/remove_param_2.png" alt="Before"/></p>
<p>
Is changed to:
changes to:
</p>
<p><img src="images/remove_param_3.png" alt="After"/></p>
<p>To remove a single parameter, a quick-assist has been added that can be activated with <b>CTRL+1</b> with the cursor located anywhere on the parameter.
Expand All @@ -120,20 +120,20 @@ <h2>Java Editor </h2>
<tr id="extend_interface_assist"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=567666 -->
<td class="title"><a href="#extend_interface_assist">Extend Interface</a></td>
<td class="content">
A new quick-assist has been added to extend an Interface. When selected, the new Interface wizard opens up.
A new <b>quick-assist</b> has been added to extend an Interface. When selected, the new Interface wizard opens up.
<p><img src="images/extend_interface_assist.png" alt="Before" /></p>
</td>
</tr>

<tr id="create_sub_type_for_sealed_type"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577317 -->
<td class="title"><a href="#create_sub_type_for_sealed_type">Create sub type for sealed super type</a></td>
<td class="content">
A new set of quick-fixes has been added to create sub-type for a sealed type which does not have any permitted types. When selected, the appropriate new Class/Record/Interface wizard opens up.
A new set of <b>quick-fixes</b> has been added to create sub-type for a sealed type which does not have any permitted types. When selected, the appropriate new <b>Class/Record/Interface wizard</b> opens up.
<p>These quick fixes have been added to fix the error :
<code>Sealed class or interface lacks the permits clause and no class or interface from the same compilation unit declares Cls1 as its direct superclass or superinterface</code></p>
<p>As shown below, two new quick fixes have been added to create sub type for a sealed super class.</p>
<p>As shown below, two new quick fixes have been added to create sub-type for a sealed super class.</p>
<p><img src="images/permitted_sub_class.png" alt="Before" /></p>
<p>As shown below, six new quick fixes have been added to create sub type for a sealed super interface.</p>
<p>As shown below, six new quick fixes have been added to create sub-type for a sealed super interface.</p>
<p><img src="images/permitted_sub_type.png" alt="Before" /></p>
</td>
</tr>
Expand Down Expand Up @@ -177,14 +177,14 @@ <h2>Debug</h2>
</tr>

<tr id="debug-stack"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=547041 -->
<td class="title"><a href="#debug-stack">Console supports stack from Debug view</a></td>
<td class="title"><a href="#debug-stack">Console support for stack from Debug view</a></td>
<td class="content">
Surprisingly enough, <b>Java Stack Trace Console</b> never supported navigation to
Java types for Java stack traces copied from <b>Debug</b> view via <b>Copy Stack</b> action.
<p>
Surprisingly enough, Java Stack Trace Console never supported navigation to
Java types for Java stack traces copied from Debug view via "Copy Stack" action.
Now the console will underline type names and line numbers and clicking on
links will jump to the corresponding source code. If the type name is not unique,
default "Select type" dialog will appear to allow selection of the right type.
Now, the console will underline type names and line numbers and clicking on
links will jump to the corresponding source code. If the type name is not unique,
default <b>Select type</b> dialog will appear to allow selection of the right type.
</p>
<p><img src="images/java_stack_console.png" alt="Console shows links to Java types"/></p>
</td>
Expand Down
32 changes: 16 additions & 16 deletions 4.24/pde.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -44,9 +44,9 @@ <h2>Plug-in Development Environment</h2>
<!-- https://github.com/eclipse-pde/eclipse.pde/issues/85 -->
<td class="title"><a href="#bundle-spy">Event Spy added to PDE</a></td>
<td class="content">
<p> The <b>Event Spy</b> allows to view the events sent using an IEventBroker and is now available via PDE, using the Spy menu or the Alt Shift F8 short cut (on windows). </p>
<p> The <b>Event Spy</b> allows to view the events sent using an <code>IEventBroker</code> and is now available via PDE, using the <b>Spies</b> menu or the <b>Alt+Shift+F8</b> shortcut (on windows). </p>
<img src="images/eventSpyMenuAndShortcut.png" alt="" />
<p>Start capturing events, and check the event's contents in the table. For instance here, the spy window has moved, and all the location events were caught.</p>
<p>Start capturing events, and check the event's contents in the table. For instance, here the spy window has moved, and all the location events were caught.</p>
<img src="images/eventSpyInPde.png" alt="" />
</td>
</tr>
Expand All @@ -55,12 +55,12 @@ <h2>Plug-in Development Environment</h2>
<!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=544838 -->
<td class="title"><a href="#auto-add-requirements-launches">Include requirements automatically when launching an application</a></td>
<td class="content">
The Launch-Configuration Wizard offers a new option in the <b>Plug-ins</b> tab to include required but missing plug-ins or features automatically while launching an Eclipse- or Equinox-application.
By default this is enabled for Launch-Configuration based on Features and disabled for those based on products, which reflects the previous behavior.
The <b>Launch Configuration</b> Wizard offers a new option in the <b>Plug-ins</b> tab to include required but missing plug-ins or features automatically while launching an Eclipse or Equinox application.
By default this is enabled for Launch Configurations based on Features and disabled for those based on products, which reflects the previous behavior.
<p>
Missing plug-ins/features are only added to the launched application but not to the Launch-Configuration.
Missing plug-ins/features are only added to the launched application but not to the Launch Configuration.
This allows to specify only the 'root' features/plug-ins you actually want in your application and to let Eclipse include only the minimal set of requirements in each launch.
Consequently new dependencies don't have to be added to the Launch-Configuration anymore.
Consequently new dependencies don't have to be added to the Launch Configuration anymore.
</p>
<p><img src="images/autoIncludeLaunch.png" alt="Automatically include requirements in launch"/></p>
</td>
Expand All @@ -79,10 +79,10 @@ <h2>Plug-in Development Environment</h2>
-->
<td class="title"><a href="#auto-add-requirements-products">Include requirements automatically when launching a product</a></td>
<td class="content">
The <b>Product-Editor</b> offers a new option in the <b>Contents</b> tab to include required but missing features or plug-ins automatically when launching the product from the IDE.
The <b>Product Editor</b> offers a new option in the <b>Contents</b> tab to include required but missing features or plug-ins automatically when launching the product from the IDE.
<p>
This controls if the corresponding option, which is described above, is activated or not for the Launch-Configuration associated with the product-launch.
By default this option is enabled for Feature and Plug-in based products to behave the same like when the product is build with Eclipse-Tycho.
This controls if the corresponding option, which is described above, is activated or not for the Launch Configuration associated with the product launch.
By default this option is enabled for Feature and Plug-in based products to behave the same like when the product is build with <b>Eclipse Tycho</b>.
</p>
<p><img src="images/autoIncludeProduct.png" alt="Automatically include requirements in product"/></p>
</td>
Expand All @@ -94,19 +94,19 @@ <h2>Plug-in Development Environment</h2>
https://github.com/eclipse-pde/eclipse.pde/pull/107
https://bugs.eclipse.org/bugs/show_bug.cgi?id=578644
-->
<td class="title"><a href="#launching-alignment">Products launched from the IDE now better behave like products build with Maven/Eclipse-Tycho</a></td>
<td class="title"><a href="#launching-alignment">Products launched from IDE now better behave like products built with Maven/Tycho</a></td>
<td class="content">
Launching a Product from within the IDE via the Product-Editor has been improved in the following aspects to result in an application whose set of Plug-ins/Features is as close as possible to what is assembled when the product is build by Maven and Eclipse-Tycho:
Launching a Product from within the IDE via the <b>Product Editor</b> has been improved in the following aspects to result in an application whose set of plug-ins/features is as close as possible to what is assembled when the product is build by <b>Maven</b> and <b>Eclipse Tycho</b>:
<ul>
<li>Launching a product based on Features creates a Feature-based Launch-Configuration</li>
<li>Launching a product based on features creates a feature-based Launch Configuration</li>
<li>Missing requirements are included by default (as described above)</li>
<li>When launching a Plugin-based product optional requirements are ignored by default when computing missing requirements</li>
<li>When automatically including requirements Fragments are not added just because their host-plug-in is included</li>
<li>When launching a plugin-based product optional requirements are ignored by default when computing missing requirements</li>
<li>When automatically including requirements, fragments are not added just because their host-plug-in is included</li>
</ul>
Together with the <a href="https://www.eclipse.org/eclipse/news/4.23/pde.php#eclipse-applications-launching">Improved launching of Eclipse/Equinox applications</a> in the previous release Eclipse 2022-03 it is now much simpler to set up products.
As an example, to create the Eclipse-SDK as a Product you only have to create a Product with basic settings via the Wizard, configure it to use Features and add the <code>org.eclipse.sdk</code> Feature.
As an example, to create the Eclipse SDK as a Product you only have to create a Product with basic settings via the Wizard, configure it to use features and add the <code>org.eclipse.sdk</code> feature.
The Product is ready to launch.
If you want git support, just add the <code>org.eclipse.egit</code> Feature and in case you want to develop Maven-Projects in your Product, just add <code>org.eclipse.m2e.feature</code>.
If you want Git support, just add the <code>org.eclipse.egit</code> feature and in case you want to develop Maven projects in your Product, just add <code>org.eclipse.m2e.feature</code>.
</td>
</tr>

Expand Down
18 changes: 8 additions & 10 deletions 4.24/platform.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -46,16 +46,16 @@ <h2>Views, Dialogs and Toolbar </h2>
</tr>

<tr id="welcomescreen"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=579463 -->
<td class="title"><a href="#welcomescreen">Welcome screen not changing the visibility of the toolbars anymore</a></td>
<td class="title"><a href="#welcomescreen">Welcome screen doesn't change toolbar visibility anymore</a></td>
<td class="content">
The welcome screen will not hide the toolbars anymore in its maximized state to behave similar like a regular view.
The Welcome screen will not hide the toolbars anymore in its maximized state to behave similar like a regular view.
</td>
</tr>

<tr id="quickaccess-filesystem"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=576341 -->
<td class="title"><a href="#codeassist-module">Find Actions can open files from file system</a></td>
<td class="content">
The <em>Find Actions</em> command, usually accessible with <b>Ctrl+3</b>, now allows to open
The <b>Find Actions</b> command, usually accessible with <b>Ctrl+3</b>, now allows to open
a file if the query is the path of an existing file on the filesystem.
</td>
</tr>
Expand All @@ -71,9 +71,9 @@ <h2>Text Editors </h2>
<tr id="multi-select-commands"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=576377 -->
<td class="title"><a href="#multi-select-commands">Action commands for multiple carets/selections</a></td>
<td class="content">
Text editors now provide various commands to support multiple carets/selections that can be bound to
<b>Text editors</b> now provide various commands to support multiple carets/selections that can be bound to
user-defined keyboard shortcuts for easy selection of text regions in text editors. No default
keys have been assigned yet (suggestions below), but can be assigned via Window/Preferences/Keys:
keys have been assigned yet (suggestions below), but can be assigned via <b>Window &gt; Preferences &gt; Keys</b>:
<dl>
<dt><b>Multi selection down relative to anchor selection</b></dt>
<dd>Search next matching region and add it to the current selection, or remove first element from current multi-selection (e.g. <b>Ctrl-Alt-J</b>).</dd>
Expand All @@ -88,7 +88,7 @@ <h2>Text Editors </h2>
<dt><b>Multi caret down</b></dt>
<dd>Add a new caret/multi selection below the current line, or remove the first caret/multi selection (e.g. <b>Ctrl-Alt-Shift-Down</b>).</dd>
</dl>
Besides that the display of multiple carets on the Windows platform has been improved to provide a
In addition to the above, the display of multiple carets on the Windows platform has been improved to provide a
more stable user experience.<br/><br/>
<img width="700" src="images/multi-selection-demo.gif" alt="multi selection demo"/>
</td>
Expand All @@ -107,12 +107,10 @@ <h2>Preferences </h2>
<tr id="explicit-encoding-workspaces"> <!-- https://bugs.eclipse.org/bugs/show_bug.cgi?id=516583 -->
<td class="title"><a href="#explicit-encoding-workspaces">Explicit encoding set for new workspaces</a></td>
<td class="content">
<p>
If Eclipse is started without explicit default encoding set, <b>UTF-8</b> will be set as default encoding
If Eclipse is started without explicit default encoding set, <b>UTF-8</b> will be set as the default encoding
for new workspaces.
</p>
<p>
In case some encoding was specified at Eclipse startup either as JVM
In case some encoding was specified at Eclipse startup either as a JVM
system property <code>-Dfile.encoding=XYZ</code>
or by product customization preference <code>org.eclipse.core.resources/encoding=XYZ</code>
, this custom encoding will be persisted as default encoding for new workspaces.
Expand Down
8 changes: 4 additions & 4 deletions 4.24/platform_isv.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ <h2>Platform and Equinox API</h2>
<tr id="ilog-service"> <!-- https://github.com/eclipse-platform/eclipse.platform.runtime/issues/33 -->
<td class="title"><a href="#ilog-service">ILog can now be acquired as a service</a></td>
<td class="content">
The ILog can now be acquired as service, so no need to have a <code>Plugin</code> activator or calling <code>Platform.getLog(...)</code> anymore if you are in a Dependency Injection Context:
The <code>ILog</code> can now be acquired as service, so no need to have a <code>Plugin activator</code> or call <code>Platform.getLog(...)</code> anymore if you are in a Dependency Injection Context:
<p>
<b>Example with E4:</b>
</p>
Expand All @@ -60,7 +60,7 @@ <h2>Platform and Equinox API</h2>
<td class="content">
<p>
There is now a new <code>EclipseContextFactory.getServiceContext(Class&lt;?&gt;)</code> method that could be used to acquire an E4 Service Context containing all OSGi services using a context class.
This becomes handy in situations where you neither has an E4 context nor an OSGi context at hand (e.g. E3 legacy code) but still want to inject some fields or create injected objects.
This becomes handy in situations where you neither have an E4 context nor an OSGi context at hand (e.g. E3 legacy code) but still want to inject some fields or create injected objects.
</p>
</td>
</tr>
Expand All @@ -71,9 +71,9 @@ <h2>Platform and Equinox API</h2>
<td id="SWT" class="section" colspan="2"><h2>SWT Changes</h2></td>
</tr>
<tr id="win32-dark-Text-search-cancel-buttons"> <!-- https://github.com/eclipse-platform/eclipse.platform.swt/issues/18 -->
<td class="title"><a href="#win32-dark-Text-search-cancel-buttons">Windows dark theme Text's search and cancel buttons</a></td>
<td class="title"><a href="#win32-dark-Text-search-cancel-buttons">Improved Text's search/cancel buttons in Windows dark theme</a></td>
<td class="content">
The windows Text widget now support improved search and cancel buttons in the dark theme:
The Windows <code>Text</code> widget now supports improved search and cancel buttons in the dark theme:
<p>
<img src="images/windows-dark-theme-text-search-cancel-buttons.png" alt=""/>
</p>
Expand Down

0 comments on commit db9824c

Please sign in to comment.