The included Forge 2 runtime is 2.10.1.Final. See the release notes here

Given that Forge 1.x is feature-frozen for some months now, we decided to remove the "Add Forge Runtime" button in the Forge preferences and keep Forge 1.4.4.Final embedded as the only choice for Forge 1.x users.

Now it’s possible to use "cd #" to navigate to the workspace location or "cd #/PROJECT_NAME" (where PROJECT_NAME is the name of the target project) to navigate to an existing project inside the current workspace.

A lot of performance improvements were made in the "JPA: Generate Entities from Tables" command.

You can find the Forge Console view in the JBoss perspective by default.

The Forge Console view now features a "Clear Console" button to clear the current output of the console.

We have added support for the "Go To Selection" (change the current resource in the console to be the selected resource in Eclipse) and "Link with Editor" (change the current resource in the console to be the selected resource in Eclipse when a file is open in the editor) console actions

We have introduced a command to allow execution of Forge 2 commands (as Eclipse Wizards) given its name. The command also allows to pass pre-populated values for the chosen Wizard.

Hibernate Tools now supports JPA 2.1 and can now work with Hibernate 4.3 (while still continuing to work with Hibernate 3.x and previous 4.x).

Due to API changes in Hibernate 4.3, the Hibernate tools API is rewired to reduce classloader issues but some issues may occur despite the implemented fixes. In the future (possibly in the next major release), Hibernate Tools will be fully decouples from the underlying Hibernate Core to continue supporting multiple versions.

JBoss Central now features a new AngularJS with Forge project wizard to let you kickstart new JavaEE based applications with HTML5 and AngularJS for the front-end, while using the powerful JBoss Forge scaffolding capabilities.

If the Forge Tool is not installed, you’ll be asked to install it. The wizard will also recommend you to install the AngularJS tooling.

Once you create the project skeleton from the new wizard, a cheatsheet will open and guide you through through the different steps necessary to use JBoss Forge and scaffold a UI layer based on AngularJS.

The Richfaces Project wizard, that was previously featured on JBoss Central, is still available in the File > New > Project…​ menu.

Target Platform is updated with the Tern.java v.0.6.0.201409041810 and JBoss Central Early Access is updated with AngularJS IDE v.0.5.0.201408281218 in order to bring the latest improvements and fixes of JavaScript and AngularJS support into JBoss Tools. AngularJS content assist and code highlighting now work in JBoss Tools HTML Editor.

Corey Daley, Ninja Hacker and Stackoverflower for OpenShift, created an extensive project page for the openshift-java-client at http://openshift.github.io/openshift-java-client/. You can get verbose instructions on how get started, sample code and where to get further help. Kudos!

Lately we introduced a commit dialog that allows you to take full control of the files being published: you can pick the files, provide the commit message etc. This commit dialog had now been simplified to have just two buttons: One to cancel and another one to commit and publish. If the only thing that you want to do is committing (without pushing), then you should be using git operations directly on the project.

Once you selected files and provided a commit message JBoss Tools will commit and push to OpenShift. If there are no local changes missing in the OpenShift remote the "Commit and Publish"-button turns to "Publish Only". The dialog will then warn you that you are only pushing local commits leaving the dirty files alone.

Our commit dialog is based on the EGit commit dialog and we thus can take advantage of existing features like the possibility to inspect changes:
Double click on the dirty files and get a visual diff of them.

When you import an OpenShift application to your workspace we add/modify a .gitignore file, possibly add an OpenShift profile to your maven pom, etc. to increase the likelihood of your project working out-of-the-box. In prior releases JBoss Tools committed those changes directly without giving you a chance to review them.

In CR1 we made publishing more explicit, we do not commit nor publish upon import. We allow you to decide what files you want to commit, what message you want to use and when you want to publish.

With the more flexible commit dialog this gives a more unified and powerful workflow.

You can now access OpenShift markers from the server adapter context menu.

The Web Services Tester is a view that helps users submit SOAP-style or plain HTTP requests on an endpoint to see how it responds.

From the "JAX-RS Web Services" node in the Project Explorer, users can select an endpoint and click on Run As>Run on Server or Debug As>Debug on Server to automatically deploy the project on an application server, have the view opened and submit a request. A dialog window will ask for values to set in the URI template if necessary.

As from JBoss Tools 4.2.0.CR1, we are starting to track usage for the Web Services Tester. In particular, we will collect the number of requests submitted with the WS Tester, per type of requests. This data will be aggregated by the Usage plugin and submitted once a day, on the following day, in order to keep the impact on the users’machines as low as possible.

Please remember that all the collected statistics are anonymous and that users can always choose to NOT send any data if they don’t want to. For more information about usage tracking, please read the documentation.