The Import wizard that you can access via File > Import Projects from Folder…​, File > Import…​ > General > Projects from Folder or File > Import…​ > Git > Projects from Git (auto-import) allows more user control. You can now see a proposal for the import (what will be imported and how) and select which sub-projects to import or exclude.

A new feature has been added to safely store your credentials for various domains in a central location. As our tools grow, credential re-use by several different features is required. Having a central place to store, for example, your Red Hat Access credentials or JBoss.org credentials, for re-use by our server adapters or download-runtime features helps to prevent you from having to constantly type the same usernames and passwords in multiple locations. It also helps to ensure that if you change your password on some remote server, you only need to update one location in eclipse.

A new Windows installer is available now to help you install Developer Studio with a full development environment for container based development using Red Hat Enterprise Linux and OpenShift.

When running an image, a launch configuration is created based on the selected image. This is useful when users want to try tweaking a previous run for various reasons (e.g. binding in new volumes or changing command parameters, etc.)

Docker Machine is now supported for the creation of a new connection. Simply click the "Search…​" button and you will be prompted to select an active Docker Machine connection, if one exists.

Containers created with a pseudo TTY allocated (-t) will open within a TM Terminal. This is much more fully featured interaction when compared with the previous standard console. In particular, the Terminal view recognizes the color code on logs and displays messages in appropriate colors.

A shortcut to build a Docker image from a Dockerfile is available. On the first call, it will prompt for the Docker connection to use and an optional name (repo/tag) to give to the image.

If your mouse pointer hovers a label, you will see the same tooltip as when the mouse hovers over the input field.

Forge now supports choosing a technology stack when creating a project:

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

When Ctrl (Or CMD in OSX) + 4 are pressed and the file is changed but not yet saved, Forge will display a confirmation dialog asking the user to save the current open file:

Freemarker library included in the Fremarker IDE was updated to latest available version 2.3.23.

Two new runtime providers for Hibernate where added with in 4.3.1.Final. Both these new versions can be selected in the relevant wizards.

This runtime includes the 5.0.8.Final version of Hibernate ORM and the 5.0.0.Alpha3 version of Hibernate Tools Core which was build using the 5.0.8.Final version of Hibernate ORM.

This runtime includes the 5.1.0.Final version of Hibernate ORM and the 5.1.0.Alpha1 version of Hibernate Tools Core which was build using the 5.1.0.Final version of Hibernate ORM.

The target platform is updated with the latest Tern.java and AngularJS-Eclipse plugins to bring the latest improvements and fixes from JavaScript Content Assistant into JBoss Tools.

OpenShift 3 was introduced as a technology preview feature in JBDS 9.0.0.GA. We’re happy to see it graduate to the level of supported feature in this release. More than 300 issues and enhancements were tackled in this version, here is an excerpt of the most noteworthy bits:

The explorer view has been simplified (and made much more robust) and focuses on an application-centric view.

You can now deploy existing workspace projects to OpenShift 3 instances. You can either create a new OpenShift application, using an OpenShift 3 connection and then select the workspace project to deploy, or you can start by right-clicking on a project and use the Configure…​ > Deploy to OpenShift…​ menu.

A new OpenShift 3 server adapter is available. Its goal is to allow incremental deployment of workspace resources directly into the deployed pods on OpenShift, bypassing the build step, to provide a much quicker turnaround.

The OpenShift 3 server adapter supports running in debug mode. When you click on the debug button, a series of actions are performed under the hood:

The OpenShift 3 server adapter supports LiveReload, accessible from the Show In > Web Browser via LiveReload Server menu. When a file is published to the server adapter, the Browser(s) connected to the LiveReload server instance will automatically refresh.

When connecting to an OpenShift instance, a dialog opens to allows users to accept/refuse untrusted SSL certificates. Those authorizations can now be reviewed and potentially revoked in a preferences page Preferences > JBoss Tools > OpenShift 3 > SSL Certificates.

A new Edit…​ menu is available in the OpenShift Explorer or the Properties view, allowing you to edit any resource (except Builds) as JSON in a text editor. This is equivalent to the oc edit command in a terminal. If a JSON editor is installed, it will be used to open the configuration, else the standard text editor will be called. When saving the configuration changes in the editor, its content will be sent to the OpenShift instance to update the underlying resource. This can be useful to, for instance, add label to resources or edit the git source URL.

When deploying a Docker image, searching for an image has never been easier. Click on the Search…​ button and find your favorite image from the selected Docker registry:

A new server adapter has been added to help start and stop the Red Hat Container Development Kit (CDK), a set of tools meant to quickly set up an OpenShift instance inside a Docker container running inside a virtual machine. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its Vagrantfile.

We’ve updated our schema catalog to include all bug-fixes or new versions, so that now your example projects targeting WildFly 10 will benefit from the same code-completion proposals that past versions have.

Windows often locks files when it shouldn’t, and this causes a big problem for filesystem-based deployments that look to make changes on-the-fly. We’ve managed to improve our integration with the WildFly application server, and to make sure we won’t make changes to files while they’re still locked by the server. Other upstream bugs in WildFly or the JDK directly are being investigated, and we look forward to having patches there in the near future.