The hover can be activated in the Java > Editor > Hovers preference page either by - selecting the Combined Hover or by clicking on the Java Constant check box.
-
The following shows hovering over an integer constant specified in octal format:
-
Here are descriptions of some of the more interesting or significant changes made to the Java development tools (JDT) -for the 4.29 release of Eclipse. +for the 4.30 release of Eclipse. They are grouped into:
See also the Eclipse Platform What's New @@ -49,37 +49,34 @@
+ The release notably includes the following Java 21 features:
+
+ JEP 440: Record Patterns.
+
+ JEP 441: Pattern Matching for Switch.
+
The hover can be activated in the Java > Editor > Hovers preference page either by - selecting the Combined Hover or by clicking on the Java Constant check box.
-
The following shows hovering over an integer constant specified in octal format:
-
default case to an enhanced switch statement. For example,
+ 
default case when it is present with unconditional pattern in a switch. For example,
+ 
break statement when there is an illegal fall-through to a pattern in a switch statement.
+ For example,
+ 
The second improvement to the lambda cleanups and quick fix is that the code now recognizes use of instanceof can - be replaced with a method reference to isInstance
. -The following code:
-
with the lambda cleanup will by default change to:
-
The functionality is also available as a quick fix for an individual call to a deprecated method that is marked with warning or error. One can also select a deprecated method call and initiate as a quick assist (select call and click CTRL + 1).
+
- This has now been inproved so that e.g. white space changes in string literals are also shown while "Ignore White Space" is active. -
-
Here are descriptions of some of the more interesting or significant changes made to the Plug-in Development Environment (PDE) -for the 4.29 release of Eclipse. They are grouped into:
+for the 4.30 release of Eclipse. They are grouped into:
- 
-
Overview page of the Product, just select
- The product configuration is based on: plug-ins and feature
- Contents page of the editor.
-
- You can launch mixed products as usual from the IDE via shortcuts in the Overview page.
- Tycho supports building mixed products since version 3.0.0.
-
Updates section to specify the Name of each update repository.
+ In the assembled product the names will be presented to a user in the preferences under Available Software Sites.
+ 
Start Levels in the Configuration page of the Product-Editor has been enhanced.
+ The Feature editor has its support for the following attributes of plugin elements removed:
Start Level configured toodownload-sizeinstall-sizeunpackfragment
feature.xml file.
+ They are ignored when present in an existing Feature and removed by the editor upon the next modification through the editor.
+
+ The Product Configuration editor has its support for the following attribute of plugin elements removed:
+
fragment.product file.
+ They are ignored when present in an existing Product and removed by the editor upon the next modification through the editor.
+
Here are descriptions of some of the changes of interest to plug-in developers -made to the Eclipse Platform and SWT for the 4.29 release of Eclipse. +made to the Eclipse Platform and SWT for the 4.30 release of Eclipse.
@@ -44,32 +44,33 @@
Control.setFocus() also activated its
- Shell. This behavior was never documented and was never
- explained why it existed. But it caused problems: setting focus
- to a control in a background Shell caused the Shell to jump on user.
+ + The org.eclipse.search bundle has been split into core and ui bundles. This will allow headless extenders to make use of the text search engine. +
+
- Now setting focus just sets focus, even if the Shell is in the background.
- To also bring Shell to front, explicitly call Shell.setActive().
-
- This change can be disabled using a Java property.
- For Example, add this VM argument in eclipse.ini or on
- the command line after -vmargs:
-Dorg.eclipse.swt.internal.activateShellOnForceFocus=true-
Note: this property is only added temporarily and will be removed later. -
- See SWT Issue 450 -
-Here are descriptions of some of the more interesting or significant changes made to the Eclipse Platform for the - 4.29 release of Eclipse. They are grouped into:
+ 4.30 release of Eclipse. They are grouped into:Plug-in developers will also be interested in the corresponding What's New in Eclipse 4.29 (Platform)
+ Plug-in developers are encouraged to migrate their E4 application model element classes to use for example
+ The support for annotations from the
+ The Eclipse SDK itself already has been migrated off these annotations from the
+ Counterintuitively the The ECF Backend used by P2 has switched to use the httpjava-client to lower the dependency chain and efforts to maintain certain third party libraries.
- This makes the placement of newly created workbench windows consistent across all operating
- systems. It also better reflects the common user expectation to have a new window placed near
- the existing one rather than on the primary monitor.
+ For now Eclipse will ship both, the new and the old backend while the newer one takes precedence. If you see any issues please proceed as follows:
+
+
+
+
+
+ Security
+
+
+
+
+
+
p2 Director Application Security
+
+ To provide similar security controls as available in the IDE,
+ the following command-line arguments are now supported the p2 director application:
+
+
+
+
+
-
@@ -55,22 +128,54 @@
General Updates
-
- Open New Workbench Window on Current Monitor
+
+
+
+
+ Support for Jakarta Annotations by Eclipse E4
+
+ The Eclipse E4 Platform Dependency Injector now supports annotations from the
+ jakarta.inject and jakarta.annotation package.
+ jakarta.inject.Inject instead of javax.inject.Inject
+ or jakarta.annotation.PostConstruct instead of javax.annotation.PostConstruct.
+ At the moment annotations from both namespaces jakarta and javax are supported.
+ javax.inject and javax.annotation package is now deprecated and will be removed in a future release, after a deprecation period of at least two years.
+ If it necessary to make a Plug-in compatible with past versions (that don't support jakarta annotations), recent and future versions (that don't support javax annotations) of the E4-Injector,
+ it can be considered to apply the annotations from both namespaces simultaneously and to import the packages from both namespaces only optionally.
+ But this strategy does not work for usages of the javax/jakarta.inject.Provider and should generally be used with caution and be verified in detail for more complex setups.
+ javax namespace to the jakarta replacements and therefore does not pull the former into a target-platform anymore.
+ If your application still needs these javax annotations you potentially have to add them explicitly to your target using entries like:
+
+
+ <unit id="jakarta.inject.jakarta.inject-api" version="1.0.5"/>
+ <unit id="jakarta.annotation-api" version="1.3.5"/>
+ javax annotations are provided by a bundle with the same symbolic name as their jakarta successor but with a 1.x version, while the jakarta successors have a 2.x version.
+ It is therefore necessary to specify the version explicitly since those bundles are not required in their latest version.
+
+
+
+
New Http Client Backend for P2
- When creating a new workbench window, it was either placed on the monitor showing the currently
- active window or on the primary monitor, depending on the operating system. Now the new window
- is always placed on the monitor that shows the active workbench window.
- In case the active workbench window spans multiple monitors, the monitor that displays the
- largest part of the active window is selected.
+
+
eclipse.ini to include -Dorg.eclipse.ecf.provider.filetransfer.excludeContributors=org.eclipse.ecf.provider.filetransfer.httpclientjava unless the problem is fixed