Arquillian Eclipse is a new JBoss Tools component that makes using Arquillian easier.

See Arquillian Eclipse.

The Arquillian support can be added/removed by right-clicking the project and selecting Configure>Add/Remove Arquillian support.

The project has to be a maven project. The Add Arquillian Support action adds the Arquillian nature to the project as well as the arquillian artifacts (bom, dependencies, required plugins, profiles …​) to the project’s pom.xml. The Remove Arquillian Support removes the Arquillian nature, but doesn’t change the project’s pom.xml.

See screencast.

The wizard is based on the JUnit Test Case wizard, but adds the following to a created class:

The user can define the name of the deployment method, the name and order of the deployment, the type and name of the archive, add an empty beans.xml, available classes and resources to the deployment archive.

See screencast.

The Generate Arquillian Deployment Method action has been added to the context menu of the Java editor and Eclipse views.

See screencast.

The Arquillian Eclipse has ability to click through to resources specified as part of Shrinkwrap definition.

See screencast.

The Run As Arquillian launch configuration includes the following features:

See screecast.

The Arquillian Validator finds the following issues:

Arquillian issues can be ignored, marked as a warning or as an error. It is possible to add quick fixes (haven’t been implemented yet) for some or all Arquillian issues.

See screencast.

The Arquillian view (Arquillia Cruiser) shows Arquillian deployment archives.

See screencast.

Arquillian Profiles can be added by right-clicking the project and selecting Configure>Add Arquillian Profiles support.

See Issue 6 for more details.

See screencast.

Arquillian Eclipse enables adding default VM arguments to Arquillian/JUnit/TestNG launch configurations.

See screencast.

New Hybrid Mobile Project wizard Creates a project structure that is compatible with the cordova-cli projects

Wizard will pre-populate your config.xml.

Provides easier editing for Cordova’s flavour of w3c widget specification XML configuration

Creates, compiles and runs the native application on the native platform emulators and devices.

CDI Tools validator reports a warning if beans.xml is missing in CDI 1.0 project. image::images/4.1.0.Beta1/beansXmlValidation.png[]

This problem can be fixed via QuickFix menu (Ctrl+1):

The embedded runtime is now Forge 1.3.0.Final!

There was a demand from our users to support the functionality offered by Forge not only in the command-line style but to also provide Eclipse-style wizards that expose this funtionality. The initial implementation of some of these wizards is now available. Note that changes to these wizards will happen according to the feedback we receive from our users.

The wizards assume that you have created a Maven enabled project, you can do this easily by creating e.g. a Java EE Web Project from the JBoss Central page.

The first important wizard is a wizard to generate entities from an existing database.

The second wizard enables you to scaffold a JSF user interface from JPA entities in your project. More scaffold types (such as html5) are on the way.

We have included Forge 2 support. The included runtime is 2.0.0.Alpha4 and as the alpha status indicates, this support is experimental. You can bring up a popup containing the available Forge 2 commands by issuing 'Ctrl+5'.

We invite you to watch this short video to get an initial idea of how to use this functionality.

The JBoss Central UI has been improved to better scale in small(er) resolutions:

JBoss Central now displays wizards for plugins that may not have been installed yet. For instance, it will display the OpenShift Application link even if you don’t have the JBoss OpenShift tooling installed. Clicking on that link will ask you to install the required OpenShift features:

Moreover that wizard list can be updated, reordered at any time, remotely from the JBoss Tools team.

As part of this change, the GWT Project wizard has been replaced by the Maven Project wizard.

OpenShift Tools have been added to the JBoss Central Software/Update page, giving users easier access to developing on and for the Cloud.

In Addition with the Directory Mode support introduced in 1.0.0.Alpha, the new Server Mode brings LiveReload support to resources deployed on a JBoss AS Server (other types of servers will follow). In this mode, the LiveReload commands are sent to the connected browsers once resources have been redeployed on the Application Server. This means that notified browsers will wait until the latest version of the resources have been deployed before loading them.

As before, users only need to create and start the LiveReload server, connect their browser using the installed extension and then start working on resources in their workspace.

The LiveReload server now features an optional embedded proxy mode which enhances the Directory Mode experience. Using this proxy, users can not only access their local files from remote devices, but also have the <script> tag to load the livereload.js script automatically inserted at the bottom of the <body> element of the returned HTML pages. This means that LiveReload support is now available for tablets and smartphones that do not allow for browser extension installation !

In the Project Explorer and Package Explorer, the contextual menu has been filled with a new "Open With>Web Browser via LiveReload Proxy" action. This latter one opens the selected file in the Web Browser, but instead of using the file:// protocol, it uses the http:// protocol and connects to the LiveReload embedded proxy.

For security reasons, the proxy is disabled by default. Once enabled, it may optionally accept remote connections if you want to enable LiveReload from remote devices or remote computers. For users wanting to use the BrowserSim with LiveReload, there is no need to allow for remote connections.

In any case, only workspace projects files are exposed by this Proxy.

Project examples plugin can now open a .cheatsheet.xml or cheatsheet.xml when a project is imported.

For now this feature must be enabled manually using the Window>Preferences>JBoss Tools>Project Examples preferences page.

There is now a new action in the "Show in" context menu: the Show in Cheat Sheets action.

This allow you to easily re-open or test a cheatsheet.xml found in examples.

The action is enabled for the Java, J2EE, JBoss and PDE perspectives.

See a screencast of this in action.

We have added new context sensitive parameterized commands for open file, show type etc. The commands can be used when creating cheatsheets.

These commands can be used like any other command in a cheatsheet. Example of this working in a project can be found at helloworld-cheatsheet

See http://screencast.com/t/gK5JggVU.

Thanks to a contribution of Carsten Pfeiffer, Visual Page Editor got experimental support for Windows 64-bit. So if you see this screen:

then you may install XULRunner from this update site (via Help > Install New Software) and make it work:

The WS Tester now uses the JBoss Wise framework to generate sample SOAP messages when testing JAX-WS services. This offers several benefits in stability and maintenance as well as a major improvement in processing complex WSDLs.