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

The Arquillian JUnit Test Case wizard has an option to add dependent classes for a class under test.

The Arquillian Working Set Filter filter shows all projects that are placed in the same working set as the selected project.

There are new Quick Fixes available for the following validation problems in Batch Job XML source editor:

The Quick Fixes open a pre-set New Batch Artifact wizard to create the missing artifact:

In this release, we have fixed a critical performance issue with JBoss Knowledge Base builder for project with large JAR libraries that contain Batch artifacts. For example, if your Maven project has a dependency on glassfish-embedded-all.jar then it could take more than 5 minutes to build the project just because of this dependency. Now, it takes seconds.

We have added icon decorators on the containers to show their state. This makes it clearer whether a container is running, paused, or stopped.

We have worked on the workflow to pull and search images from Docker Hub. The updated Pull Image wizard can be launched from the Docker Images view or from the Docker Explorer view (a new context menu entry is available on the connection node and on the Images node)

The wizard detects the tag in the image name and if none is specified, the image tagged latest is pulled.

If the user needs to search a specific image name, she can click on the Search…​ button which will open the Search wizard:

This is followed by a second page that displays all the tags for the selected image:

Even though this wizard can only search from Docker Hub, users can still pull images from other third-party registries. When doing this, the image name must contain a prefix with the registry host and port, for example 192.168.59.103:5000/centos:7.

We have also added a new launcher to build images from a Dockerfile.

The source path is a directory in the workspace or on the file system and the Docker Connection combo box specifies on which Docker daemon the image will be built.

The interface for the connection wizard has not changed, but at the back end, it has been rewritten to better validate the input settings. The wizard now requires a unique name to identify the connection and checks the required permissions on the Unix socket and on the path to the certificates for TCP connections.

The included Forge runtime is 2.19.2.Final.

Start the Forge runtime using the Ctrl+4 (or Cmd+4) key combination.

The following new core Hibernate Tools releases have been published:

These four new releases with their specific Hibernate ORM dependencies have been included in the corresponding Hibernate runtime provider plugins in the 4.3.0.CR1 release of JBoss Tools.

The wizard to create new Hibernate configuration files (*.cfg.xml) now supports multiple Hibernate versions.

A new dropdown box now allows for the selection of the desired Hibernate version.

JBoss Tools and JBoss Developer Studio’s Target Platforms have been updated with the latest Tern.java and AngularJS-Eclipse features to bring the latest improvements and fixes of JavaScript Content Assistant into JBoss Tools.

Check out their New and Noteworthy pages:

Note: These features are available via JBoss Central - Early Access, as a part of AngularJS for Web Tools

JSDT now includes an option to turn off internal parsing and validation, which is useful for users working with big projects where JavaScript is not the main part of development by reducing the memory/performance requirements. This option is also useful when JSDT is used with third-party tools which provide Content Assisting and Validation for JavaScript.

For such projects the "External Builder/Validator" mode can be selected for ECMAScript compliance level preference on the Window→Preferences→JavaScript→Validator preference page:

See: Bug 472754 - Provide a way to turn off any parsing/validation/search indexing by internal JSDT parser

Some entries in the Software/Update page will now be shown only for the purpose of information. These cannot be installed immediately into JBoss Tools, but may instead represent software that is still being prepared and will be available soon.

We have made great progress in the OpenShift 3 Eclipse Tooling, but a few features are still missing, like deploying an existing workspace project, or editing existing build configurations. We have some ideas to provide an even better OpenShift Explorer user experience.

OpenShift 3 tooling is provided as a TechPreview feature, available from the JBoss Central Software/Updates page. Once we are fully satisfied with the quality of its feature set, OpenShift 3 tooling will mature to a Supported feature in the upcoming months, and will then be installed by default in JBDS.

Because OpenShift 3 concepts and behavior are quite different from OpenShift 2, we thought it would be a good idea to display a link to the online documentation from the connection wizard for OpenShift 3. Hopefully that should help you get started with OpenShift 3 in Eclipse.

The New OpenShift 3 application wizard contains the following enhancements in this release:

A number of new features have been added to the OpenShift Explorer for an improved user experience:

The Port Forwarding and Log Streaming features require that the OpenShift Client (OC) binary is installed on your machine. If the OC binary is missing, an error dialog will prompt you to configure its location in the OpenShift 3 preferences. If you don’t have a local copy of the OC binary, a link guides you to its download page.

Provided the OC binary was set up in Eclipse’s preferences, you can now, from the OpenShift Explorer, stream logs from Build (Build Log…​ menu) or Pod (Pod Log…​) nodes. This is the same feature as Tail Log in OpenShift 2.

Logs display in a Console view, allowing users to monitor builds or application server logs in real time.

The OpenShift 3 Eclipse Tooling now provides some integration with the Docker tooling with further improvements coming soon. Docker images can be deployed to the OpenShift cluster with an initial set of OpenShift resources. The Deploy Image wizard can be initiated from either the OpenShift or Docker explorer views. This wizard allows you to:

As mentioned in the JBoss Central section, you now have access to over 200 project examples from the JBoss Central page. All these examples and their dependencies can now be cached locally via the Groovy Offline script, available from Preferences > JBoss Tools > Project Examples > Offline Support.

Groovy 2.4.x is now required to execute the offline script.

Please be aware the script now takes several hours to complete (3h on the Red Hat build farm).

Minor improvements include the inclusion of new server adapters for JBoss EAP 7 and WildFly 10 to the toolset, allowing you to enjoy all the past benefits, but with all the newest runtimes.

We have now verified that WildFly can be run on the newest builds of Java 9 with Jigsaw. This support is only built into our WildFly 10 adapters by default, but users of earlier application servers can remove the -jaxpmodule javax.xml.jaxp-provider portion of the launch arguments to get the same support.