Latest posts

When it comes to login to a cluster, OpenShift Tools supported two different authentication mechanisms:

The drawback is that it does not cover clusters where a more enhanced and modern authentication infrastructure is in place. So it is now possible to login to the cluster through an embedded web browser.

In order to use it, go to the Login context menu from the Application Explorer view:

Click on the Retrieve token button and an embedded web browser will be displayed:

Complete the workflow until you see a page that contains Display Token:

Click on Display Token:

The web browser is automatically closed and you’ll notice that the retrieved token has been set in the original dialog:

Since JBoss Tools 4.18.0.Final, the preferred way of developing components is now based on devfile, which is a YAML file that describe how to build the component and if required, launch other containers with other containers. When you create a component, you need to specify a devfile that describe your component. So either you component source contains its own devfile or you need to pick a devfile that is related to your component. In the second case, OpenShift Tools supports devfile registries that contains a set of different devfiles. There is a default registry (https://github.com/odo-devfiles/registry) but you may want to have your own registries. It is now possible to add and remove registries as you want.

The registries are displayed in the OpenShift Application Explorer under the Devfile registries node:

Please note that expanding the registry node will list all devfiles from that registry with a description:

A context menu on the Devfile registries node allows you to add new registries, and on the registry node to delete it.

Although devfile registries can provide ready-to-use devfiles, there may be some advanced cases where users need to write their own devfile. As the syntax is quite complex, the YAML editor has been completed so that to provide:

Python-based components were supported but debugging was not possible. This release brings integration between the Eclipse debugger and the Python runtime.

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

A server adapter has been added to work with Wildfly 23.

The server adapter has been adapted to work with EAP 7.4 Beta.

Enjoy!

Jeff Maury

The Application Explorer view is now based on odo 2.x, which allows deployments to be based on devfile (developer oriented manifest file). The components from the default odo registry are listed with legacy S2I components:

It is also now possible to bootstrap from an empty project as the components from the registry may expose starter projects (sample code that will initialize your empty project).

code.quarkus.io has added a new option codestart that allows extension that support this new feature to contribute sample code in the generated project. It is enabled by default and is accessible from the second step in the wizard:

A server adapter has been added to work with Wildfly 22.

A number of additions and updates have been performed on the available Hibernate runtime providers.