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

If JBoss Tools is run on an older Java version, a warning dialog appears:

A new diagram tab of Batch Job Configuration editor allows to graphically draw structure of a batch job XML file.

Content assist works for any class attribute (used to reference exception classes). Just type the first letter of the class or name and the content assist will show all available proposals.

A new Batch Artifact wizard is available in New→Others→Batch menu and allows to create batch artifacts, such as:

The "Run BrowserSim" command is now available in the "Quick Access" for every single perspective:

Now an optional url parameter can be added to the BrowserSim command when writing Cheet Sheets. The usage is the following:

The connection wizard support both Unix sockets and REST API to connect to a Docker engine

The new "Docker Explorer" view displays containers and images in a tree view, with filters to hide dangling and intermediate images and stopped containers.

The new "Containers" view displays the same information that appears when using the docker ps or docker ps -a commands in a terminal.

The new "Images" view displays the same information that appears when using the docker images command in a terminal.

The new "Run Image" wizard lets users run an image by passing the most relevant arguments in the context of a developer machine:

The wizard also lets users search and pull images from the Docker Registry.

The Properties view responds to the selection on an Image or a Container in the aforementioned views to display general and detailed information.

The pull, push, display logs, commit, and tag commands are also available from contextual menus and view toolbars.

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

This release includes a slick, new and improved JBoss Central. This is a HTML-based page designed to provide instant access to a large variety of JBoss Developer materials. From top to bottom, you have access to :

The new and improved search feature provides instant access to approximately 200 quickstarts, filtered with zero latency as you type:

Click on a given tag to perform a search using that tag’s label.

We are really proud of how the new JBoss Central page gracefully adapts to lower resolutions, thanks to the Bootstrap framework under the hood. We really hope you’ll appreciate it as well. Please don’t hesitate to provide your feedback.

The Target Platform is updated with the latest Tern.java and AngularJS-Eclipse to bring the latest JavaScript Content Assistant improvements and fixes into JBoss Tools.

Review information about the note and noteworthy features here:

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

Starting with JBoss Tools 4.3.0.Beta1 you can now connect and authenticate to an OpenShift v3 server configured to use OAuth. You retrieve a token by clicking the retrieve link, following the prompts in the browser, and pasting it back into the connection wizard.

"OpenShift v3" is not available online yet, as it is for OpenShift v2 at https://www.openshift.com/. If you want to check it out, you can run it from with vagrant, as described here: http://fabric8.io/guide/openShiftWithFabric8Vagrant.html

You can now use templates to create OpenShift v3 resources that make up an application. The wizard allows you to use a template offered by the server, or to provide a template that you have ready on your local file system.

Once the template is selected, you can edit the template parameters to customize it for your needs.

You can add labels so that you will be able to reference those new resources once they are created.

You can easily point your browser to your OpenShift v3 application via the context menu. Pick your project in the OpenShift explorer and choose menu:[Show In>Web Browser] and it will open up in the browser.

OpenShift routes are used to figure out the url to open to your application. If there are several routes, you will choose the one to use.

An OpenShift v3 application can now be imported into Eclipse using JBoss Tools. The import wizard prompts you to select a build config which contains the URI of your source repository. The wizard clones the source repository and imports the code into your Eclipse workspace as an Eclipse project.

All source repositories are imported as general Eclipse projects that you can manually configure to match your needs, except those which utilize Maven. Maven is recognized by the import process and the Eclipse projects are enabled via Eclipse’s Maven support. Eclipse project type detection will be improved in upcoming releases via the new Eclipse "Smart Import" facility.

4.3.0.Beta1 will show you OpenShift v3 routes in the OpenShift Explorer, as they have been defined in your OpenShift project. The properties view unveils all details for the selected route.

You can now delete OpenShift v3 resources that you browse in the OpenShift explorer.

As mentioned in the JBoss Central section, the JBoss Central page now provides over 200 project examples.

However, these examples are not yet integrated in the Project Examples wizard, nor completely supported by the Offline support mechanism: After running an example once, it will be available even if your internet connection goes down, but the groovy script in Preferences > JBoss Tools > Project Examples > Offline Support will not fetch and cache these new examples.

These issues will be addressed in the next Beta release.

Support for Port Monitoring has been (finally) added to JBoss, WildFly, and our enterprise server adapters. With a preference page, a view for tracking recent past requests, integration with the servers view, and some custom enhancements of our own, JBoss Tools is confident that our integration with this WebTools feature is more complete than what’s available with other server adapters.

A blog entry has been posted with further details.

A new feature hiding in the CDT repository of eclipse is being released with Mars. Called the LaunchBar, this feature aims to update the UI of eclipse to allow for more easy running of launch configurations (and other things). In this Beta1 release, we’re adding this feature in an optional addition to our Server Tools. We’ve also written our own extensions to it, integrating the LaunchBar with WTP’s Server Adapters.

The list of launchable objects (center) is linked with your selections in the workspace when used with our extensions, in most cases before you’ve ever even launched the object. The list of targets (on the right) will include all existing server adapters compatible with the launchable.

To enable this feature, you need to install from Help > Install New Software…​ > http://download.jboss.org/jbosstools/mars/development/updates then select the JBoss Tools Server LaunchBar Integration feature.

For more information, you can also check launchbar’s documentation at eclipse.org, or try it for yourself.

The SWT Browser name and version is now collected for usage statistics to help the JBoss Tools team to learn more about preferred user configurations.

All collected information is reflected in Preferences > JBoss Tools > Usage Reporting for the user’s review.

As always, JBoss Tools does not send any information unless a user has opted into this option, nor is there ever any personal information sent.

Content assist for methods in Websocket endpoint classes is now added.

Websocket endpoint classes are classes annotated with javax.websocket.server.ServerEndpoint or javax.websocket.ClientEndpoint. They can have methods annotated with @OnClose, @OnError, @OnMessage, @OnOpen.

Content assist provides the following options:

Each option can only be used once. After being used once, the option does not appear in the choices.

Use Content assist from any position to add a new class member. Use prefixes to reduce the choice list. For example, if onO or @onO is typed and Content Assist is invoked, only onOpen choice will be suggested.

Example of inserted code: