Posts tagged with 'release'

The old Hibernate Runtimes for versions 5.4, 5.5, 6.0, 6.1, 6.2, 6.3, and 6.4 are now disabled by default.

Multiple additions and updates have been performed on the available Hibernate runtime providers.

In JBoss Tools, a fresh perspective has been introduced, known as the "RSP Servers View," which utilizes the Runtime Server Protocol (RSP). More information on this page.

However, this feature was not available on the JBossTools update site. This has been resolved and now the feature appears as "Runtime Server Protocol Server Tooling by Red Hat", under the "JBoss Application Server Adapters" category.

As outlined and announced in a prior blog post, the subsequent components have been excluded from the latest JBoss Tools distribution:

Multiple additions and updates have been performed on the available Hibernate runtime providers.

In JBoss Tools, a fresh perspective has been introduced, known as the "RSP Servers View," which utilizes the Runtime Server Protocol (RSP).

To begin, you must initiate the server connector responsible for managing the servers. Simply right-click on any entry for the Server connector, and choose the "Start RSP" option.

The server connector is now starting and it’s status will change to [STARTED].

You can then choose between download a server or use a local server.

Now, let’s create a new server. Simply right-click on the active Server connector and select "Download Server." Choose any runtime from the list and confirm by clicking OK.

Follow the dialog steps for additional parameters and wait for the installation to finish. You can see a new entry on the server view with the selected server.

Now start the server runtime using "Start Server" context menu action. The console view opens and display any message from the server.

Now you can add any deployment to the server. This can be either a folder or a file, present on your local computer. For example, let’s deploy a basic web application.

Right click on the started server runtime and select "Add deployment". Then select a web archive to be added to the server.

It will automatically deploy the application and display any message in the console.

Now you can enjoy the application on your browser !

We are welcoming any suggestion to this new view, either on our JIRA/Github, or using our gitter chatroom

As communicated in a previous blog article, the following components are now deprecated:

The current openshift Application Explorer view, based on odo v3 is now the default supported tooling.

The Hibernate 6.2 runtime provider now incorporates Hibernate Core version 6.2.5.Final, Hibernate Ant version 6.2.5.Final and Hibernate Tools version 6.2.5.Final.

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

Fuse Tooling is now deprecated. More information here.

As previously announced here, we’ve removed the Central / update tab, SEAM and JSF support from JBossTools.

For central update tab, all the existing central extensions can be installed with the marketplace client, using the entries listed here.

The Hibernate 6.2 runtime provider incorporates Hibernate Core version 6.2.3.Final, Hibernate Ant version 6.2.3.Final and Hibernate Tools version 6.2.3.Final.

The Hibernate 6.2 runtime provider now incorporates Hibernate Core version 6.2.0.CR4, Hibernate Ant version 6.2.0.CR4 and Hibernate Tools version 6.2.0.CR4.

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.

As previously announced, we removed some components in this release :

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.13.Final and Hibernate Tools version 5.6.13.Final.

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

Java 17 is now a minimum requirement to run JBoss Tools. JBoss Tools continues to support running servers and applications with older Java versions.

The Quarkus extension ecosystem is composed of extensions that are part of the platform and the others. The Quarkus project wizard has been extended to allow exclusion of extensions that are not part of the platform.

A new runtime provider has been added for Hibernate 6.1. It incorporates Hibernate Core version 6.1.3.Final and Hibernate Tools version 6.1.3.Final.

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