{"id":107835,"date":"2019-11-11T07:30:52","date_gmt":"2019-11-11T07:30:52","guid":{"rendered":"https:\/\/developers.redhat.com\/blog\/?p=649017"},"modified":"2019-11-11T07:30:52","modified_gmt":"2019-11-11T07:30:52","slug":"new-features-in-red-hat-codeready-studio-12-13-0-ga-and-jboss-tools-4-13-0-final-for-eclipse-2019-09","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2019\/11\/11\/new-features-in-red-hat-codeready-studio-12-13-0-ga-and-jboss-tools-4-13-0-final-for-eclipse-2019-09\/","title":{"rendered":"New features in Red Hat CodeReady Studio 12.13.0.GA and JBoss Tools 4.13.0.Final for Eclipse 2019-09"},"content":{"rendered":"

JBoss Tools 4.13.0<\/a> and Red Hat CodeReady Studio 12.13<\/a> for Eclipse 2019-09 are here and waiting for you. In this article, I’ll cover the highlights of the new releases and show how to get started.<\/p>\n

<\/span><\/p>\n

Installation<\/h2>\n

Red Hat CodeReady Studio<\/a> (previously known as Red Hat Developer Studio) comes with everything pre-bundled in its installer. Simply download it from our Red Hat CodeReady Studio product page<\/a> and run it like this:<\/p>\n

java -jar codereadystudio-<installername>.jar<\/pre>\n
JBoss Tools or Bring-Your-Own-Eclipse (BYOE) CodeReady Studio requires a bit more.<\/p>\n
This release requires at least Eclipse 4.13 (2019-09), but we recommend using the latest Eclipse 4.13 2019-09 JEE Bundle<\/a> because then you get most of the dependencies pre-installed.<\/p>\n
Once you have installed Eclipse, you can either find us on the Eclipse Marketplace under “JBoss Tools” or “Red Hat CodeReady Studio.”<\/p>\n
For JBoss Tools, you can also use our update site directly:<\/p>\n
http:\/\/download.jboss.org\/jbosstools\/photon\/stable\/updates\/<\/pre>\n
What’s new?<\/h2>\n
Our main focus for this release was improvements for container-based development and bug fixing. Eclipse 2019-06 itself has a lot of new cool stuff, but I’ll highlight just a few updates in both Eclipse 2019-06 and JBoss Tools plugins that I think are worth mentioning.<\/p>\n
Red Hat OpenShift<\/h3>\n
OpenShift Container Platform 4.2 support<\/h4>\n
With the new OpenShift Container Platform (OCP) 4.2<\/a> now available (see the announcement<\/a>), even if this is a major shift compared to OCP 3, Red Hat CodeReady Studio and JBoss Tools are compatible with this major release in a transparent way. Just define your connection to your OCP 4.2 based cluster as you did before for an OCP 3 cluster, and use the tooling!<\/p>\n
CodeReady Containers 1.0 Server Adapter<\/h4>\n
A new server adapter has been added to support the next generation of CodeReady Containers 1.0. Although the server adapter itself has limited functionality, it is able to start and stop the CodeReady Containers virtual machine via its crc binary. Simply hit Ctrl+3 (Cmd+3 on OSX) and type new server<\/code>, which will bring up a command to set up a new server.<\/p>\n
\"crc<\/p>\n
Enter\u00a0crc<\/code>\u00a0in the filter textbox.<\/p>\n
You should see the\u00a0Red Hat CodeReady Containers 1.0<\/em>\u00a0server adapter.<\/p>\n
\"\"<\/a><\/p>\n
Select\u00a0Red Hat CodeReady Containers 1.0<\/em> and click Next<\/em>.<\/p>\n
\"\"<\/a><\/p>\n
All you have to do is set the location of the CodeReady Containers crc binary file and the pull secret file location, which can be downloaded from https:\/\/cloud.redhat.com\/openshift\/install\/crc\/installer-provisioned<\/a>.<\/p>\n
\"\"<\/a><\/p>\n
Once you\u2019re finished, a new CodeReady Containers server adapter will then be created and visible in the Servers view.<\/p>\n
\"\"<\/a>Once the server is started, a new OpenShift connection should appear in the OpenShift Explorer<\/em> view, allowing the user to quickly create a new Openshift application and begin developing their AwesomeApp in a highly replicatable environment.<\/p>\n
\"\"<\/a>Server tools<\/h3>\n
Wildfly 18 Server Adapter<\/h4>\n
A server adapter has been added to work with Wildfly 18. It adds support for Java EE 8 and Jakarta EE 8.<\/p>\n
EAP 7.3 Beta Server Adapter<\/h4>\n
A server adapter has been added to work with EAP 7.3 Beta.<\/p>\n
Hibernate Tools<\/h3>\n
Hibernate Runtime Provider Updates<\/h4>\n
A number of additions and updates have been performed on the available Hibernate runtime providers.<\/p>\n
The Hibernate 5.4 runtime provider now incorporates Hibernate Core version 5.4.7.Final and Hibernate Tools version 5.4.7.Final.<\/p>\n
The Hibernate 5.3 runtime provider now incorporates Hibernate Core version 5.3.13.Final and Hibernate Tools version 5.3.13.Final.<\/p>\n
Platform<\/h3>\n
Views, Dialogs and Toolbar<\/h4>\n
Quick Search<\/h5>\n
The new\u00a0Quick Search<\/em>\u00a0dialog provides a convenient, simple and fast way to run a textual search across your workspace and jump to matches in your code. The dialog provides a quick overview showing matching lines of text at a glance. It updates as quickly as you can type and allows for quick navigation using only the keyboard. A typical workflow starts by pressing the keyboard shortcut\u00a0Ctrl+Alt+Shift+L\u00a0(or\u00a0Cmd+Alt+Shift+L\u00a0on Mac). Typing a few letters updates the search result as you type. Use\u00a0Up-Down\u00a0arrow keys to select a match, then hit\u00a0Enter\u00a0to open it in an editor.<\/p>\n
\"\"<\/a><\/p>\n
Save editor when Project Explorer has focus<\/h5>\n
You can now save the active editor even when the\u00a0Project Explorer\u00a0has focus. In cases where an extension contributes\u00a0Saveables\u00a0to the Project Explorer, the extension is honored and the save action on the Project Explorer will save the provided saveable item instead of the active editor.<\/p>\n
\"\"<\/a><\/p>\n
“Show In” context menu available for normal resources<\/h5>\n
The\u00a0Show In<\/em>\u00a0context menu is now available for an element inside a resource project on the\u00a0Project Explorer<\/em>.<\/p>\n
\"\"<\/a><\/p>\n
Show colors for additions and deletions in Compare viewer<\/h5>\n
In simple cases such as a two-way comparison or a three-way comparison with no merges and conflicts, the Compare<\/em> viewer now shows different colors, depending on whether text has been added, removed, or modified. The default colors are green, red, and black, respectively.<\/p>\n
\"\"<\/a><\/p>\n
The colors can be customized through usual theme customization approaches, including using related entries in the\u00a0Colors and Fonts preference\u00a0page.<\/p>\n
Editor status line shows more selection details<\/h5>\n
The status line for\u00a0Text Editors\u00a0now shows the cursor position, and when the editor has something selected, it shows the number of characters in the selection as well. This also works in the block selection mode.<\/p>\n
These two new additions to the status line can be disabled via the\u00a0General > Editors > Text Editors<\/em>\u00a0preference page.<\/p>\n
\"\"<\/a><\/p>\n
\"\"<\/a><\/p>\n
Shorter dialog text<\/h5>\n
Several dialog texts have been shortened. This allows you to capture important information faster.<\/p>\n
Previously:<\/p>\n
\"\"<\/a><\/p>\n
Now:<\/p>\n
\"\"<\/a><\/p>\n
Close project via middle-click<\/h5>\n
In the\u00a0Project Explorer, you can now close a project using middle-click.<\/p>\n
Debug<\/h4>\n
Improved usability of Environment tab in Launch Configurations<\/h5>\n
In the\u00a0Environment <\/em>tab of the Launch Configuration<\/em>\u00a0dialog, you can now double-click on an environment variable name or value and start editing it directly from the table.<\/p>\n
\"\"<\/a><\/p>\n
Right-clicking on the environment variable table now opens a context menu, allowing for quick addition, removal, copying, and pasting of environment variables.<\/p>\n
\"\"<\/a><\/p>\n
Show Command Line for external program launch<\/h5>\n
The\u00a0External Tools Configuration<\/em>\u00a0dialog for launching an external program now supports the\u00a0Show Command Line<\/em>\u00a0button.<\/p>\n
\"\"<\/a><\/p>\n
Preferences<\/h4>\n
Close editors automatically when reaching 99 open editors<\/h5>\n
The preference to close editors automatically is now enabled by default. It will be triggered when you have opened 99 files. If you continue to open editors, old editors will be closed to protect you from performance problems. You can modify this setting in the\u00a0Preferences\u00a0<\/em>dialog via the\u00a0General > Editors > Close<\/em>\u00a0editors automatically preference.<\/p>\n
In-table color previews for Text Editor appearance color options<\/h5>\n
You can now see all the colors currently being used in\u00a0Text Editors<\/em>\u00a0from the Appearance<\/em> color options table, located in the\u00a0Preferences > General > Editors > Text Editor<\/em>\u00a0page.<\/p>\n
\"\"<\/a><\/p>\n
Automatic detection of UI freezes in the Eclipse SDK<\/h5>\n
The Eclipse SDK has been configured to show stack traces for UI freezes in the\u00a0Error Log\u00a0view by default for new workspaces. You can use this information to identify and report slow parts of the Eclipse IDE.<\/p>\n
\"\"<\/a><\/p>\n
You can disable the monitoring or tweak its settings via the options in the\u00a0General > UI Responsiveness Monitoring<\/em>\u00a0preference page as shown below.<\/p>\n
\"\"<\/a><\/p>\n
Themes and Styling<\/h4>\n
Start automatically in dark theme based on OS theme<\/h5>\n
On Linux and Mac, Eclipse can now start automatically in dark theme when the OS theme is dark. This works by default, that is on a new workspace or when the user has not explicitly set or changed the theme in Eclipse.<\/p>\n
Display of Help content respects OS theme<\/h5>\n
\n
More and more operating systems provide a system-wide dark theme. Eclipse now respects this system-wide theme setting when the Eclipse help content is displayed in an external browser. A prerequisite for this is a browser that supports the prefers-color-scheme CSS media query.<\/p>\n
As of the time of writing, the following browser versions support it:<\/p>\n