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.

Performance is also significantly improved, and importing a Maven project will now suggest installation of m2e connectors when necessary.

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.

To access the central credential storage, browse to Window > Preferences > JBoss Tools / Credentials. From there, add custom domains for which you wish to store credentials, or add username/password combinations to the two pre-existing domains: access.redhat.com and jboss.org.

At this time, only Download Runtimes and the new (experimental) CDK Server Adapter use this new framework. However, usage is expected to increase in the future across the toolset as the tool matures.

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.

The Installer currently only works on 64-bit Windows only and is currently available as a Technology Preview.

The Red Hat JBoss Developer Studio Platform installer sets up the following components on your machine:

Please register on developers.redhat.com to get access to the Platform.

Here is a short demo of the new installer: https://youtu.be/dMWAguol3as

Important: Ensure that Virtualization is enabled in the BIOS settings for your machine. This is required to run VirtualBox and Vagrant. For further information, consult your system’s documentation for instructions to change BIOS settings.

JBoss Tools is now targeting Eclipse Mars.2 as a running platform.

Hybrid mobile tools now use Cordova CLI for Cordova plugin management and platform builds. This allows us to provide accurate build and Cordova plugin management that is compatible with the latest Apache Cordova releases.

This new feature uses Cordova CLI installed on your system and guides you through installation if they are missing.

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.)

Running a container from an image can now be also done via a launch configuration.

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.

The launch configuration also now supports most of the build options available from CLI.

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:

In addition to setting up your project, choosing a stack automatically hides some input fields in the existing wizards, such as the JPA Version in the JPA: Setup wizard:

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:

You can check the Always save before opening the command dialog checkbox to avoid displaying the confirmation dialog. This setting can be changed anytime in the Preferences dialog under the Forge category:

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.

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.

Read more about their New and Noteworthy features here:

Note: These features are available via JBoss Central - Early Access as a part of AngularJS for Web 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:

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.

Simply hit Ctrl+3 (Cmd+3 on OSX) and type CDK, that will bring up a command to setup and/or launch the CDK server adapter. All you have to do is set the credentials for your Red Hat account and the location of the CDK’s Vagrantfile. Once you’re finished, a new CDK Server adapter will then be created and visible in the Servers view.

Once the server is started, Docker and OpenShift connections should appear in their respective views, allowing the user to quickly create a new Openshift application and begin developing their AwesomeApp in a highly-replicatable environment.

Right-click on a running CDK server adapter and select an option in the Show In menu to display the OpenShift or Docker Explorer:

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.

In addition, several schema had small updates, bugfixes, and documentation changes. All of these will be available in the XML Catalog now.

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.

With your permission, Eclipse and Red Hat JBoss Developer Studio can inspect errors logged inside the IDE and inform project committers about the issues you’ve experienced. This optional service, called Automated Error Reporting Initiative (AERI), can report issues to both the Eclipse Bugzilla and the JBoss JIRA.

When the first error is logged, you’ll be asked if you’d like to participate in error reporting, which is by default completely anonymous and only happens if an error occurs.

Should you want to configure how the service operates, or provide your email address so that you could be contacted regarding any reports you submit, open Preferences > General > Error Reporting. You can then click Configure Projects…​ to enable or disable reporting to Eclipse or JBoss.

As always, neither Eclipse nor JBoss will use any information unless a user has opted in, nor is there ever any personal information sent unless it is provided on the Preferences page.