Now you can specify which JVM is used to launch BrowserSim/CordovaSim. This allows to run BrowserSim/CordovaSim from 64-bit Eclipse on Windows. To specify JVM go to Window > Preferences > BrowserSim/CordovaSim and choose a suitable JVM (32-bit JRE/JDK 6 or JDK 7 (but not JRE 7) on Windows):

The usability of these wizards has been improved a lot.

The wizards are now in the 'JBoss Tools→Forge' category and have an icon.

When using the 'Entities From Tables' wizard, there is now a way to create a project should you not have one available yet. Clicking the 'New…​' button next to the project dropdown box opens another wizard to do this work.

In the 'Entities From Tables' wizard, it is now possible to browse for the driver jar and the driver classes.

The scaffold wizard now offers the possibility to choose between faces and angularjs. Also the set up step has been removed and the two wizard pages have been merged into one.

There is now also wizard support for generating REST endpoints for entities. It is very similar to the scaffolding wizard.

Additionally, as you might have noticed in all of the above screenshots, these wizards now have nice progress bars that indicate what is happening under the covers.

The included runtime is now 2.0.0.Alpha5. The popup that results from issuing 'Ctrl+5' now looks a lot better. It also contains a few more Forge 2 commands.

Coming in JBoss Tools 4.1.0.Beta2, LiveReload now also supports 'Server Mode', which brings the same level of features to deployed resources than what was introduced in JBoss Tools 4.1.0.Beta1 for the 'Directory Mode' for workspace resources:

Having the proxy with both 'livereload.js script injection' and 'allow remote connections' options enabled makes a perfect combination to test applications on smartphones and tablets, especially when the LiveReload Browser Extension cannot be installed on such devices.

However, typing the entire URL on such devices is not a good experience. This is why JBoss Tools now provides with a dialog showing a QR Code for such use-cases. Users just need to select the network interface on which they will connect and then scan the generated QR Code with their devices to get access to the resource. The dialog also displays an hyperlink to open the location in the external browser.

Coming in JBoss Tools 4.1.0.Beta2, the proxy option now becomes a permanent feature of the LiveReload server, which means that even workspace resources will be opened with the HTTP protocol instead of the File protocol.

The following use-case have been implemented:

Note: In case where the user wants to display the QRCode to test with a mobile device, script injection and remote connections should be enabled.

We now provide a groovy script that pre-caches all JBoss Tools examples and their dependencies for anyone wanting to be able to work offline (after an initial online session). For instance, an instructor can download all the required dependencies and then provide a zipped .m2/repository to his students via flash drive, all students can then work offline.

A groovy command with proper arguments is generated under Preferences > JBoss Tools > Project Examples > Offline Support.

Click on the copy to clipboard button and then paste the clipboard in a terminal. An offline/ directory will be created in the directory the script is run under.

All Example archives will be downloaded under offline/.jbosstools/cache. They will then be built -if based on Maven- and the Maven dependencies will populate a clean offline/.m2/repository. The whole process takes typically around 30 minutes on a 20MB broadband connection.

The generated offline cache should be copied under ${user.home}/.jbosstools/cache (that location can be changed in Preferences > JBoss Tools > Project Examples > Offline Support). The maven repository should be copied over to your local repository.

Once the "Enable offline mode for project examples" button is checked (after saving the preferences), Examples will be fetched from the offline directory and no remote connection will be attempted to get the example data. Switching Offline mode will also switch m2e’s offline mode, if the maven examples feature is installed.

wildfly.org have been announced, with builds available of WildFly 8.

New Server Type is introduced to add WildFly support for Server creation, deployment and runtime detection.

The WS Tester used to have JAX-WS as the default test type in the drop-down. As much of our effort has been towards RESTful services, we have changed the default test type to a RESTful GET operation.