Chapter 1. Introduction to Red Hat JBoss Developer Studio

Users can now specify labels when running a container. The labels are saved in the launch configuration and can also be edited before relaunching the container.

View larger image

See issues 498166, 497777, 485913 and 485936 in Eclipse Bugzilla for more details.

When the Docker Explorer view is opened, the list of existing connections (saved from a previous session) is reloaded. Additionally, the view finds new connections using default settings such the unix:///var/run/docker.sock Unix socket or the DOCKER_HOST, DOCKER_CERT_PATH and DOCKER_TLS_VERIFY environment variables. This means that by default, in a new workspace, if a Docker daemon is reachable using one of those methods, the user does not have to use the New Connection wizard to get a connection.

See issue 497101 in Eclipse Bugzilla for more details.

An extension point has been added to the Docker core plugin to allow for custom connection settings provisioning.

See issue 497100 in Eclipse Bugzilla for more details.

Support for Docker Compose is now available. Users can select a docker-compose.yml file and start Docker Compose from the context menu, using the Run > Docker Compose launcher shortcut.

The Docker Compose process displays it logs (with support for text coloring based on ANSI escape codes) and provides a stop button to stop the underlying process.

View larger image

Also, as with the support for building and running containers, a launch configuration is created after the first call to Docker Compose on the selected docker-compose.yml file.

See issue 479592 in Eclipse Bugzilla for more details.

The new Docker Image Hierarchy view lets the user view the layers for a selected image in the Docker Explorer view. This is useful when an image was built locally, as it helps understanding on which layers the top-level image depends.

View larger image

See issue 496308 in Eclipse Bugzilla for more details.

The included Forge runtime is now 3.3.1.Final. Read the official announcement here.

View larger image

From Forge 3.3.0.Final onwards it is now possible to query and install add ons listed in the Forge add ons page.

View larger image

The Freemarker library included in the Freemarker IDE was updated to the latest available version 2.3.25.

Related JIRA: JBIDE-22700

The new flth and fltx extensions are added and associated with Freemarker IDE. flth refers to HTML content and fltx refers to XML content.

Related JIRA: JBIDE-22636

The parser that FreeMarker IDE uses to extract IDE-centric information (needed for syntax highlighting, related tag highlighting, auto-completion, outline view, etc.) was overhauled.

Several bugs were fixed, and support for the newer template language features were added. Also, the syntax highlighting is now more detailed inside expressions.

Related JIRAs: JBIDE-20180, JBIDE-22574, JBIDE-21819

Fixed the issue when the (by default) yellow highlighting of the related FTL tags shift away from under the tag as you type.

Related JIRA: JBIDE-22656

The standard "Show whitespace characters" and "Toggle block selection mode" icons are now available when editing a template.

Related JIRA: JBIDE-22751

When you type symbols such as <#, <@, ${, and #{, the Freemarker editor now automatically closes them.

Related JIRA: JBIDE-22749

When a FreeMarker exception is printed to the console, the error position in it is a link that navigates to the error. This has worked long ago, but was broken for quite a while.

Related JIRA: JBIDE-22701

When hitting enter, sometimes the new line haven’t inherited the indentation of the last line.

Related JIRA: JBIDE-20512

Auto completion now knows all directives and "built-ins" up to FreeMarker 2.3.25.

Related JIRAs: JBIDE-20386, JBIDE-22765

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

1.5.4.1.1. New Hibernate 5.2 Runtime Provider

Copia collegamento

With final releases available in the Hibernate 5.2 stream, the time was right to make available a corresponding Hibernate 5.2 runtime provider. This runtime provider incorporates Hibernate Core version 5.2.2.Final and Hibernate Tools version 5.2.0.Beta1.

View larger image

Server templates are now displayed in the property view under the Templates tab:

View larger image

You can access/edit the content of the template with the Edit option.

Related JIRA: JBIDE-22457

Events generated as part of the application life cycle now display in the Properties view under the Events tab (available at the project level):

View larger image

You can refresh the content of the event with the Refresh option or open the event in the OpenShift web console with the Show In Web Console option.

Related JIRA: JBIDE-22817

Volume claims are now displayed in the Property view under the Storage tab (available at the project level):

View larger image

You can create a new volume claim using a resource file:

{
    "apiVersion": "v1",
    "kind": "PersistentVolumeClaim",
    "metadata": {
        "name": "claim1"
    },
    "spec": {
        "accessModes": [ "ReadWriteOnce" ],
        "resources": {
            "requests": {
                "storage": "1Gi"
            }
        }
    }
}

{
    "apiVersion": "v1",
    "kind": "PersistentVolumeClaim",
    "metadata": {
        "name": "claim1"
    },
    "spec": {
        "accessModes": [ "ReadWriteOnce" ],
        "resources": {
            "requests": {
                "storage": "1Gi"
            }
        }
    }
}

If you deploy such a resource file with the New Resource option at the project level, the Storage tab is updated:

View larger image

You can access/edit the content of the volume claim with the Edit option or open the volume claim in the OpenShift web console with the Show In Web Console option.

Related JIRA: JBIDE-22433

Runtime detection has been included in JBoss Tools for several releases, but it sometimes creates runtimes and server adapters with configuration errors without alerting the user. Now, the user has an opportunity to execute quick fixes before completing the creation of their runtimes and servers.

View larger image

For example, at the runtime-detection preference page, the runtime-detection automatically searches the three paths for valid runtimes of any type.

View larger image

When you click Search, the runtime-detection’s search dialog appears with the results. In this case, it has located an EAP 6.4 and an EAP 7.0 installation. However, we can see that both have errors. If we click on the error column for the discovered EAP 7.0, the error is expanded, and we see that a valid/compatible JRE is missing. To fix the issue, click this item.

View larger image

A new JRE dialog box appears when you click on the problem for EAP 7, which is used to add a compatible JRE. The dialog informs us of what the restrictions are for this specific runtime. In this case, a JRE with a minimum version of Java 8 is required.

View larger image

If you locatie and add a Java 8 JRE, as shown above, all the errors disappear for both runtimes. In this example, the EAP 6.4 required a JRE of Java 7 or higher. The addition of the Java 8 JRE fixed this issue as well.

View larger image

This dialog is intended to help preemptively discover and fix errors before using the created server adapters.

Related JIRA: JBIDE-15189 - Add quickfixes to runtime detection