Posts tagged with 'jbosscentral'

The Hibernate 6.0 runtime provider (Preview) now incorporates Hibernate Core version 6.0.2.Final and Hibernate Tools version 6.0.2.Final.

The Hibernate 5.6 runtime provider now incorporates Hibernate Core version 5.6.9.Final and Hibernate Tools version 5.6.9.Final.

The Hibernate 5.3 runtime provider now incorporates Hibernate Core version 5.3.27.Final and Hibernate Tools version 5.3.27.Final.

The Hibernate 6.0 runtime provider (Preview) now incorporates Hibernate Core version 6.0.2.Final and Hibernate Tools version 6.0.2.Final.

The Hibernate 5.6 runtime provider now incorporates Hibernate Core version 5.6.9.Final and Hibernate Tools version 5.6.9.Final.

The Hibernate 5.3 runtime provider now incorporates Hibernate Core version 5.3.26.Final and Hibernate Tools version 5.3.26.Final.

The Hibernate 6.0 runtime provider (Preview) now incorporates Hibernate Core version 6.0.0.CR2 and Hibernate Tools version 6.0.0.CR2.

The Hibernate 5.6 runtime provider now incorporates Hibernate Core version 5.6.7.Final and Hibernate Tools version 5.6.7.Final.

The Hibernate 4.3 runtime provider now incorporates Hibernate Tools version 4.3.6.Final.

The Hibernate 3.6 runtime provider now incorporates Hibernate Tools version 3.6.2.Final.

The Hibernate 3.5 runtime provider now incorporates Hibernate Tools version 3.5.3.Final.

The Hibernate 6.0 runtime provider (Preview) now incorporates Hibernate Core version 6.0.0.CR1 and Hibernate Tools version 6.0.0.CR1.

The Hibernate 5.6 runtime provider now incorporates Hibernate Core version 5.6.5.Final and Hibernate Tools version 5.6.5.Final.

The platform now embeds Apache Log4j 2.17.1.

So the following CVEs:

have been fixed.

As Apache Log4j 1.x is also embedded but is not maintained anymore, the Apache Log4j bundle (1.2.15) has been patched in order to remove:

The Hibernate 6.0 runtime provider (Preview) now incorporates Hibernate Core version 6.0.0.Beta2 and Hibernate Tools version 6.0.0.Beta2.

The Hibernate 5.6 runtime provider now incorporates Hibernate Core version 5.6.3.Final and Hibernate Tools version 5.6.3.Final.

The Hibernate 5.5 runtime provider now incorporates Hibernate Core version 5.5.9.Final and Hibernate Tools version 5.5.9.Final.

The Hibernate 5.4 runtime provider now incorporates Hibernate Core version 5.4.33.Final and Hibernate Tools version 5.4.33.Final.

The Hibernate 5.3 runtime provider now incorporates Hibernate Core version 5.3.25.Final and Hibernate Tools version 5.3.25.Final.

The Hibernate 5.2 runtime provider now incorporates Hibernate Core version 5.2.13.Final and Hibernate Tools version 5.2.13.Final.

The Hibernate 5.1 runtime provider now incorporates Hibernate Core version 5.1.12.Final and Hibernate Tools version 5.1.12.Final.

The Hibernate 5.0 runtime provider now incorporates Hibernate Core version 5.0.7.Final and Hibernate Tools version 5.0.7.Final.

A new runtime provider has been added for Hibernate 5.6. It incorporates Hibernate Core version 5.6.0.Beta2 and Hibernate Tools version 5.6.0.Beta2. This runtime is in preview mode.

The Hibernate 5.5 runtime provider now incorporates Hibernate Core version 5.5.7.Final and Hibernate Tools version 5.5.7.Final.

The Hibernate 5.3 runtime provider now incorporates Hibernate Core version 5.3.22.Final and Hibernate Tools version 5.3.22.Final.

Before accepted licenses were only remembered during runtime and not persisted between restarts. The user selection of accepted licenses is now persisted between restarts.

When installing a software into the workbench and the software is signed but with an untrusted certificate, the dialog to review trusted certificates now shows a button to 📥 Export…​ the selected certificate into their own *.der file. This can facilitate review of the certificate, for example in order to get it audited by some other external service, tool or workflow before approval.

The Quick Search dialog features a label to depict the number of matches that were found. Additionally, if the result set exceeds a now configurable limit, the label shows that the limit has been reached and the search process stops. Besides this new "Max Results" configuration option, the preference page has been overhauled with information decorators to describe the properties in more detail.

The drawing of the close icon of tabs has been updated to align better with the operating system.

Old:

New:

Eclipse on Windows now support dark-theme tool-tips. Refer below screens-shot which show various tool-tips@dark-theme:

The Local history for derived files is now disabled by default. The behaviour can now be configured to the previous (enabled) behaviour in Preferences > General > Workspace > Local History page, by checking the History for derived files checkbox.

Derived files are for example automatically created as the output of java annotation processing or XText. As they are automatically created one could also recreate old versions of the output by compiling older versions of the input, thereby wasting time and space to store the history of the derived files for most users.

Eclipse SDK downloads for the Mac AArch64(Arm64) architecture are now available. Please note that a Mac AArch64 JVM is required to run Eclipse for Mac AArch64. Eclipse for Mac AArch64 will be formally supported in the Target Environments in a future release.

Eclipse and SWT for Mac x86_64 architecture can already run on Apple Silicon hardware under Rosetta translation mode using a x86_64 JVM.

GridDataFactory contains a new static method create(int style) which returns a new GridDataFactory instance. This method is similar to new GridData(int style).

SWT now requires minimum Java 11 to run SWT.

Eclipse has adopted Ant version 1.10.11.

The bundle required execution environment (BREE) for the org.eclipse.jdt.junit.runtime and org.eclipse.jdt.junit4.runtime bundles is now JavaSE-1.8.

A new clean up has been added that converts code to use StringBuilder (added in Java 1.5) rather than StringBuffer which has synchronized methods and is slower than using StringBuilder.

There is a sub-option where changes will only occur to local variables which is on by default. When this sub-option is on, changes will only occur to StringBuffer variables that are local to a method. When a method calls other methods with such variables or assigns to/from fields/parameters, the method contents will not be converted. It is permitted to append StringBuffer fields or parameters to local StringBuffer variables which can then still be converted to StringBuilder.

When the option is selected and the sub-option for local variables is off,all usage of StringBuffer in the selected files are changed to StringBuilder regardless of usage. It should be noted that in this case, the clean up will not track down non-selected classes and methods that are referenced and might require changes to compile successfully.

To apply the clean up, select the Use StringBuilder instead of StringBuffer check box on the Performance tab in your clean up profile. To specify just for local variables, select the Only for local variables check box found just below.

For the given code:

One gets:

A new quick-assist has been added to convert appropriate while loops into do/while loops. Appropriate while loops require the first evaluation of the while expression is guaranteed to be true and that the evaluation is passive.

For the following loop:

One is offered:

The Extract Superclass refactoring has been enhanced to support movement of uninitialized non-static final fields. In the past, a warning was issued for extracting uninitialized non-static final fields as the resultant code would be in error. The refactoring has been enhanced to add additional parameters to the moved constructors and to pass initialization values from the original class constructors.

For the following class:

Extracting to Superclass and choosing all fields, one gets:

and

A new menu item has been added for doing a raw paste when editing Java files. The menu item Raw Paste can be found in the Edit pull-down menu and by right-clicking in the edit window to bring up the context-menu. The menu item performs a paste action but toggles off the smart insert feature, if required, and restores it, if necessary, after the paste. For end-users in smart insert mode, this is the same as doing a Shift+Ctrl+Insert followed by Ctrl+V, followed by Shift+Ctrl+Insert to retoggle into smart insert mode again.

Default values have been added to the Java > Appearance > Type Filters preferences. Types matching these filters will be excluded from appearing in the Open Type dialog, content assist, quick fix, and organize imports. These filter patterns do not affect the Package Explorer and Type Hierarchy views.

A new quick fix (Ctrl+1) has been added to change the project compliance and JRE when multi-constant case labels are used in a project below Java 14:

You can use the following quick fix (Ctrl+1) to declare a sealed interface as super interface of its permitted types:

You can use the following quick fix (Ctrl+1) to declare a sealed class as super class of its permitted classes:

You can use the following quick fix (Ctrl+1) to add a sub type to permitted types of a sealed super type:

The quick fix Create a new local variable has been enhanced. When it creates a variable that is the expression on which a foreach loop iterates, its type is an array of the type of the loop parameter:

For the given code:

One gets:

A new clean up has been added that uses an instanceof expression to check an object against a hardcoded class.

The expression must be a supertype of the targeted class.

To apply the clean up, select Use instanceof keyword instead of Class.isInstance() check box on the Code Style tab in your clean up profile.

For the given code:

One gets:

A new clean up has been added that replaces (X && Y) || (X && Z) by (X && (Y || Y)).

The operands must be passive and primitive.

To apply the clean up, select Replace (X && Y) || (X && Z) by (X && (Y || Z)) check box on the Duplicate code tab in your clean up profile.

For the given code:

One gets:

A new clean up has been added that moves a duplicate inner if condition around an outer if condition.

The inner if condition should be common to both if/else clauses of the outer if statement.

The if conditions should be passive.

To apply the clean up, select Pull out a duplicate 'if' from an if/else check box on the Duplicate code tab in your clean up profile.

For the given code:

One gets:

A new clean up has been added that merges consecutive if statements with same code block that end with a jump statement.

To apply the clean up, select Single 'if' statement rather than duplicate blocks that fall through check box on the Duplicate code tab in your clean up profile.

For the given code:

One gets:

A new clean up has been added that replaces the check of the emptiness of String.strip() by the use of String.isBlank().

It avoids the cost of the creation of a stripped string.

You may use Java 11 or higher to use it.

In order to apply this cleanup also to trim().isEmpty(), you might consider to replace trim(), which exists since the beginning of Java, with strip() that has been introduced in Java 11 together with isBlank(),

But watch out, trim() and strip() differ: trim() removes leading and trailing characters with an ASCII code up to 32, including some non white space ASCII control characters and missing some Unicode white space characters, whereas strip() removes all and only leading and trailing white space.

To apply the clean up, select String.isBlank()` rather than `String.strip().isEmpty() check box on the Optimization tab (the Performance tab in Eclipse 2021-09) in your clean up profile.

For the given code:

One gets:

A new clean up has been added that replaces unnecessary primitive wrappers instance creations by using static factory methods (valueOf()).

It dramatically improves the space performance.

To apply the clean up, select valueOf() rather than instantiation check box on the Optimization tab (the Performance tab in Eclipse 2021-09) in your clean up profile.

For the given code:

One gets:

A new clean up has been added that replaces a primitive wrapper object by the primitive type when an object is not necessary.

The variable must be not null. The result should not make more autoboxing/unboxing than the original code.

To apply the clean up, select Primitive type rather than wrapper class check box on the Optimization tab (the Performance tab in Eclipse 2021-09) in your clean up profile.

For the given code:

One gets:

A new clean up has been added that directly checks boolean values instead of comparing them with true/false.

The operator can be equals, not equals or XOR. The constants can be a literal or a java.lang.Boolean constant. One operand should be primitive so no new null pointer exceptions may occur.

To apply the clean up, select Boolean value rather than comparison check box on the Unnecessary Code tab in your clean up profile.

For the given code:

One gets:

A new clean up has been added that removes the comparator declaration if it is the default one.

The declared comparator should be an equivalent to the natural order. It removes anonymous class, lambda, Comparator.comparing(), Comparator.naturalOrder() and null. It applies on List.sort(Comparator), Collections.sort(List, Comparator), Collections.max(Collection, Comparator) and Collections.min(Collection, Comparator). If the comparator is used in the method List.sort(Comparator), the method is converted into Collections.sort(List).

To apply the clean up, select Use implicit comparator when possible check box on the Unnecessary Code tab in your clean up profile.

For the given code:

One gets:

A new clean up has been added that replaces the new instance syntax by curly brackets to create an array.

It must be an initialization of a declaration. The declaration must have the same type.

To apply the clean up, select Create array with curly when possible check box on the Unnecessary Code tab in your clean up profile.

For the given code:

One gets:

A new clean up has been added that removes unnecessary local variable declaration or unnecessary variable assignment before a return statement.

An explicit type is added for arrays.

To apply the clean up, select Remove variable assignment before return check box on the Unnecessary Code tab in your clean up profile.

For the given code:

One gets:

A new clean up has been added that replaces certain System.getProperty() calls with alternative Java method calls or constants instead. Using these calls/constants may end up using system defaults (e.g. system default file separator) and thus can no longer be overridden at runtime.

To apply the clean up, select Replace system property with constant check box on the Java Feature tab in your clean up profile. This enables you to check one or more sub-options: File separator, Path separator, Line separator, File encoding, or Boolean property. The last option is used for arbitrary boolean options specified by -Dsome-arbitrary-option.

For the given code:

One gets:

External annotations, which are used for annotation based null analysis, can now be associated to unannotated classes more freely.

Previously, all external annotations where declared per build path entry. I.e., whenever a project of yours uses a library for which external annotations exist, you would need to explicitly declare where the corresponding external annotations for this particular library can be found.

A new compiler preference has been added by which you can instruct the compiler to search for external annotations in all build path locations of the current project.

When enabled, this strategy will be applied to all class files encountered during compilation.

Some examples, where this option is useful:

For batch compilation a corresponding option already exists. To match the above strategy in CI-builds, just add the following to the compiler command line (verbatim): -annotationpath CLASSPATH

The Search view now supports a new filter dedicated for static imports. Consequently, the existing imports filter is dedicated for non-static imports only. As a result, you will now by default find statically imported references of a class or an interface.

Create module-info.java option has been moved to the first page of New Java Project creation wizard. This option will be enabled only for Java projects with JRE 9 or above. New Java Project creation wizard will also remember the previous choice made by the user and select this option by default accordingly.

The default cleanup profile of the Java development tools has been updated to include more cleanups. All included cleanups have been well tested and proven to be stable in the Eclipse code base. Please see the preference under Java > Clean-up for details.

In debug mode, regardless of the selected stack frame now you can evaluate variables which are in the scope of the current execution stack frame and stack frames below it which are defined in the current focused java class.

A new Copy button has been added to the Dependencies/Classpath tab of Run Configuration dialog. This can be used to copy the details of the selected item.

When hovering over chain of variables, the debug hover will now show the variable value under the cursor.

It even works for array length.