Latest posts

As previously announced here, we’re in the process to remove the Central / update tab from JBossTools in next release. This work can be followed here.

That means that all the current extra features that can be installed via this tab needs to be available through a new channel. This channel already exists as p2 repo, but using Eclipse Marketplace Client is more close to what’s existing right now.

Most of those additional features are already present in the Jboss marketplace entry, so it’s just a matter of use it to install your favorite feature.

The missing create service feature that was available with odo 2.X is now back in this release.

See the previous annoucement on this feature

Once you have created a service, you can link it to a component using a binding.

A new Hibernate 6.2 runtime provider incorporates Hibernate Core version 6.2.0.CR2, Hibernate Ant version 6.2.0.CR2 and Hibernate Tools version 6.2.0.CR2.

The Hibernate 6.1 runtime provider now incorporates Hibernate Core version 6.1.7.Final, Hibernate Ant version 6.1.7.Final and Hibernate Tools version 6.1.7.Final.

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

As planned and communicated in a previous blog article, the following components have been removed from the JBoss Tools distribution:

Please note that the following components are obsoleted so they are still part of this JBoss Tools distribution but they will be removed from the next JBoss Tools release:

The OpenShift Application Explorer view based based on odo 2.x in previous versions of JBoss Tools. It already leverages the power of devfiles to describe your development environment, odo 3.x enhances and simplifies the workflow.

With odo 3.x, you can create a component (unit of deployment) from your source files and once the component is created, you can start it in dev mode: a new deployment will be created on the cluster, application will be built on the cluster and then, each time you modify some of the source files on your local workstation, the change will be broadcasted to the remote cluster.

In order to test your application, you can open a browser of the OpenShift Application Explorer and browse your application running on the cluster.

Once your component is running in dev mode, you can start a local debugger (Java, Node.js, Python) that will connect to the deployment on the cluster and let’s you troubleshoot and analyze more complex use cases.

This addresses the inner loop style of development where you can get instant feedback on your changes.

odo 3.x also supports outloop style of development: once you think your application in ready to be deployed on an staging, integration or production cluster, you can start your component in deploy mode: a new image defined by yourself will then be built and deployed on the cluster.

In the following example, we will start from a Quarkus application generated from https://code.quarkus.io, create the component, start the dev mode, check that we can access the application, start the debugger and check that we can reach a breakpoint.

The Hibernate 6.1 runtime provider now incorporates Hibernate Core version 6.1.5.Final, Hibernate Ant version 6.1.5.Final and Hibernate Tools version 6.1.5.Final.

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

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