JBoss Tools is now targeting Eclipse Luna.

In Luna M4 there currently are known issues with Eclipse SWT and GTK3 on various Linux distribution like Fedora 20.

You can try run with EXPORT SWT_GTK3=0 which make SWT used GTK2 which might will reduce some crashes.

The Arquillian XML Editor makes Arquillian tests easier to configure.

The editor has been created using the Sapphire framework (http://www.eclipse.org/sapphire). It includes the following features:

See http://screencast.com/t/058KgoS7ZK0 and http://screencast.com/t/s16HzZEzmx

The Create Arquillian Deployment Method action scans for all, direct and indirect dependencies. Those dependencies can be automatically added to the deployment using the Create Arquillian Deployment Method wizard.

Now, the Arquillian validator uses AST to search for dependencies. This way, performance are significantly improved because we don’t have to create Arquillian archive(s) anymore. Likewise, the Arquillian validator is implemented as an Eclipse builder instead of JDT compiler participant which improves its stability.

The Arquillian validator checks if an archive name extension matches an archive type.

See screencast

The Add Arquillian Support dialog is significantly improved. A user can decide if he wants to change the pom.xml file, which sections to change as well as which arquillian version to use. There is also the pom.xml preview page.

Arquillian includes a new Quick Fix.

related_jiras::JBIDE-14528[]

Arquillia Cruiser View contains a filter to filter active projects.

Double-clicking an archive resource in the Arquillia Cruiser view opens the resource in the associatted Eclipse editor.

It is possible to get Content Assistant on 'cordova' Object as well as on its Properties and Methods in JavaScript.

There is a new "Show Installed" check box to show already installed Cordova plug-ins on a project.

Now there is a Linux specific option (enabled by default) to enable GTK2 for the process launched by BrowserSim / Cordovasim. It allows using javaFx web engine and debugger on Linux:

Now Cordovasim uses the same engine (cordova.js) as HMT (Hybrid Mobile Tools) and handles it in an appropriate way:

Now the output of the main javascript console functions (console.log, console.info, console.warn, console.error) is displayed in the Eclipse console. The option is now available for both SWT WebKit and JavaFx web engines:

Now CordovaSim has Battery Status support. It gives the ability to simulate batterystatus, batterylow and batterycritical events.

Now every time when CordovaSim can’t handle a plug-in, the following prompt is displayed:

Notifications can also be disabled in the Settings tab of CordovaSim’s preferences :

JavaFx is an alternative to SWT WebKit and enables Windows users to run BrowserSim and CordovaSim without having to install Safari and run these features with a 32-bit Java developer kit.

In past 32-bit was assumed/forced giving problems for users on 64-bit Windows. Now the BrowserSim and CordovaSim will be launched with the appropriate version without the user to start.

If you are on 32-bit Windows you can still install Safari to use SWT WebKit if preferred.

Process launch console output is implemented for both SWT WebKit and JavaFx web engines. Not only the output of the main javascript console functions (console.log, console.info, console.warn, console.error) is displayed in the Eclipse console, but also logs and errors of the process. Also user can manipulate console (Pin Console, Scroll Lock, etc.) and close BrowserSim / CordovaSim via Terminate button.

Linked folders are honored when project is run on CordovaSim.

CordovaSim now supports query parameters for the start page in launch configuration and via content tag in the config.xml.

CDI Tools now support CDI 1.1 projects. If your CDI project (with enabled CDI support) has CDI 1.1 jars in its classpath, CDI Tools will recognize it as CDI 1.1 project automatically. There is no need to use any special settings to distinguish CDI 1.0 from CDI 1.1 in CDI Tools.

CDI tools recognize now DeltaSpike partial beans which are taken into account by the related tools features such as validation, code completion, hyperlinks, refactoring, etc.

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.

The included Forge 2 runtime is 2.7.2.Final.

The popup dialog containing the available Forge commands now shows the most recent choices at the top.

As shown in the previous image, the popup dialog with the available Forge commands now shows the current selection from where the popup was opened. Also the wizards that are launched show this current selection in the title bar.

We provided deep integration between the Forge 2 database add-on and the Eclipse DTP project. Connection profiles created with Forge 2 can be used in DTP and the other way around.

Bring up the connection profile wizard as illustrated below.

Fill out the fields to create the desired connection profile and push Finish.

Et voila, you can see the newly created profile in the DTP Data Source Explorer. Moreover you can connect to the data source and view the contents of the tables as illustrated below.

The embedded Forge console can now also be used with the included Forge 2 runtime.

You can switch between both consoles using a drop down menu in the Forge console toolbar.

Very good news for Forge 2 users! Forge 2 went final in the meantime and we included runtime version 2.3.0.Final.

Lots of useful new commands have been implemented in the meantime. Bring up the list of available commands using the Ctrl+5 (or Cmd+5) keystroke.

The embedded Forge 1 runtime is now Forge 1.4.4.Final!

The included Forge 2 runtime is 2.6.0.Final.

Starting the Forge 2 runtime is now achieved using the Ctrl+4 (or Cmd+4) key combination, the same as for Forge 1 runtimes. When multiple Forge runtimes are installed this key combination starts the default Forge runtime, which is specified and changeable in the Forge preferences.

As well as starting the Forge runtime, pressing Ctrl+4 (or Cmd+4) opens a window listing available Forge wizards. The list of wizards is responsive, changing based on the currently selected workspace object. The image below illustrates the available wizards when nothing in particular was selected.

As you can see, there are wizards for creating database connection profiles, for managing Forge addons and for creating a new project.

When a project is selected while pressing the magic key combination, more wizards become available as illustrated in the image below.

The wizards above are also available as commands on the Forge command line. Open the Forge Console by navigating through the Eclipse menu (Window→Show View→Other…​→Forge→Forge Console) or by typing in the Quick Access text field.

The image below illustrates the available commands in the workspace root.

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.

JBoss Central now features the Hybrid Mobile Project wizard to let you kickstart new Cordova-based mobile applications.

If the Hybrid Mobile Toolkit is not installed, you’ll be asked to install it, as well as a few useful companion features (CordovaSim, BrowserSim). When using JBoss Tools you’ll also be offered to add LiveReload and the Visual Plugin Editor, if these features are not already installed.

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

We have introduced the concept of 'Early Access' features that can be installed from the Software/Updates tab of JBoss Central. These features are experimental or still being developed, so they may contain bugs and may not yet behave correctly.

To support these new incubating features, we’ve updated the JBoss Central view.

From the same JBoss Central Software/Updates page used to install additional features, you can now update features (if a newer version is available), or uninstall them.

Content Assistant in JavaScript is extended with the proposals on Objects, Properties and Functions of ECMA5 JavaScript Specification

If you have AngularJS Eclipse Plugin installed in your Eclipse then JBoss Tools will enable AngularJS support in JavaScript projects automatically. For such projects, JBoss Tools HTML editor now provides AngularJS specific code assist, navigation, etc.

AngularJS Eclipse Plugin is available for installation in the Software/Update tab of JBoss Central (you need to enable Early Access features first).

Since JBoss Tools 4.2.0.Beta2, jQuery Mobile Palette supports multiple versions of jQuery and jQuery Mobile JS/CSS files in the New Widget dialog.

If there are no jQuery files references in the HTML page when inserting a jQuery Mobile widget from the Palette, then the corresponding JS and CSS links are added to the header element of the page automatically by default (can be disabled).

Drag and Drop from jQuery Mobile Palette was improved and inserts widgets in proper places on the page, not just wherever the cursor/mouse happens to be. For example if you trying to drop a new page into another page then the page will be inserted right after or before the existing page element. If there is no proper place for the widget then a warning message will be shown:

There is now one more way to insert an HTML5 widget from the Palette view. All palette entries are available via content assist (Ctrl+Space) as templates.

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.

Target Platform is updated with the Tern.java v.0.4.0.201407030911 in order to bring the latest improvements and fixes of JavaScript Content Assistant into JBoss Tools:

In this release we introduce an initial support for Ionic widgets in the HTML5 palette view.

It’s now possible to ignore non-standard HTML attributes. We contributed that feature to Eclipse Luna (Milestone 6). This is typically needed when developing Angular JS applications as the HTML validator considers Angular JS ng-* attributes as invalid html (which is actually correct since the proper syntax to be 100% compatible with the html5 spec is to use data-ng-*).

With this change we hope to now strike the right balance between those liking strict and those preferring relaxed validation.

When a widget from Palette view is dragged and dropped the corresponding New Widget wizard is opened to let you fine tune the content. This is great for beginners and complex tags but if you just want the default text you can now hold down Ctrl (for Linux and Windows) or Alt/Option (for Mac) and now when the widget is dropped to the HTML Editor the code snippet is inserted without any dialog.

Faster and more efficient.

New Heading widget (introduced in jQuery Mobile 1.4) is now available in HTML5 Palette view.

Prior to JBoss Tools 4.2.0.CR2 one could not deploy JEE 7 projects to OpenShift. The OpenShift server adapter complained that it was not supporting version 3.1 of the J2EE Web module specification. In this new milestone we now fixed this.

JBoss Tools could not connect to OpenShift when run on openjdk 1.7/Linux while the server was running on Red Hat Enterprise 6.6. OpenJDK 1.8, Oracle JDKs, Windows and MacOS machines were not affected. This was caused by the server offering DHE cipher keys larger than 1024 bits. The cipher provider in openjdk 1.7/linux were not able to handle these and failed handshaking (see https://bugzilla.redhat.com/show_bug.cgi?id=1131221). OpenJDK fixed this bug with openjdk-1.7.0.71 (see https://rhn.redhat.com/errata/RHSA-2014-1633.html). For our users that are stuck with the failing combination we offer the following system property that disabels the faulty DHE ciphers: We now allow you to disable the causing cipher with the following system property (the flag is off by default):

You can add this to your eclipse.ini and avoid the problem.
We also provide an automatic mode where we test the jdk for it’s ability to handle DHE cipher keys > 1024 bits and disable the DHE ciphers accordingly:

When you try to deploy an existing project to OpenShift the tooling gladly assists you and adds the OpenShift maven profile to the pom.xml in your project. When using a Wilfly 8.1 Quickstart the tooling created an incorrect outputDirectory in the OpenShift profile causing the deployment to fail. We fixed this for CR2.

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.

JBoss Tools 4.2.0.Beta adds New/Import OpenShift Application to the configure context menu of your workspace project in the package explorer and navigator. This allows you to create a new OpenShift application for your project via its the context menu. Simply pick Configure → New/Import OpenShift application and we’ll present you the application wizard.

Once the OpenShift application is created, we’ll merge it into your project. Pushing it back via our server adapter or via (E)git will deploy your project to OpenShift.

In JBoss Tools 4.2.0 Beta2 you will be able to start new applications from the promoted OpenShift quickstarts. A quickstart will configure the appication-, add-on cartridge(s) and the application template code for you.

The quickstarts comes with predefined list of cartridges for setup. If that list allows you to choose between versions you can Edit them.

Snapshots allow you to backup and restore your OpenShift application to and from a .tar.gz archive. Full snapshots contain all local files of your application, including the logs.

There is more than just backup and restore in snapshots: Binary deployments are also possible via Deployment snapshots. Deployment Snapshots allow you to deploy to OpenShift without using git.

JBoss Tools allows you both full and deployment snapshot via radio buttons in the snapshot wizard.
You can read all the details about (deployment) snaphots in the OpenShift user guide

We geared towards making your life easier and added all application related actions to the OpenShift server context menu (Servers view). We also reorganized the context menu of the OpenShift Explorer to better match the defaults used in Eclipse.

OpenShift allows you to add and remove other users to your domain and grant them view or write permissions. In JBoss Tools 4.2.0.Beta3 we added a link to the domain wizard. Hitting this link points your browser to the webpage in the OpenShift where you can manage your domain members.

JBoss Tools 4.2.0.Beta3 now allows you to pick the files that you want to publish. Once you tell the OpenShift server adapter to publish, it checks the pending changes and lists them in a dialog. You may then stage the ones you want to push and provide a commit message.
The very same is true for the inital import of your OpenShift application: The application-/import-wizard lists the files it changed and allows you to commit and push them back to OpenShift.

You can now save and restore your OpenShift application snapshots to and from your Eclipse workspace:

A new mobile application example, contacts-mobile-basic, has been added to the Mobile Applications category of project examples. This example, featured in the Start from a sample section of JBoss Central, combines an Apache Cordova-based front-end client, communicating with an Apache Maven-built, JAX-RS-based back-end service.

Usage reporting is now able to track individual events besides just pure startups. In this beta we activated two kinds of event tracking.

These we will use to learn more about how our users are using the tooling and improve tooling going forward.

All information which is going to be collected is reflected in Preferences for you to review:

As always JBoss Tools will not send any information before a user have opted in, nor is there any personal information sent.

A few new usage events have been added to this milestone release:

These will be used to learn more about how our users are using the tooling and improve it going forward.

All information which is going to be collected is reflected in Preferences > JBoss Tools > Usage Reporting for you to review.

As always JBoss Tools will not send any information before a user have opted in, nor is there any personal information sent.

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.

JVM name and architecture (32/64 bit) are now collected for usage statistics to help JBoss Tools team to learn more about how our users are using the tooling. JBoss Tools also tracks events when the runtime detection mechanism creates a new server.

All information which is going to be collected is reflected in Preferences > JBoss Tools > Usage Reporting for you to review.

As always JBoss Tools will not send any information before a user have opted in, nor is there any personal information sent.

HTML Preview is a WYSIWYG plugin for HTML pages. Preview is not coupled with a particular editor, but editor must have DOM model support. HTML Preview has several cool features like:

HTML Preview can be enabled via Quick Access > HTML Preview. More info about HTML Preview can be found in our blog.

HTML Preview could also be treated as a possible XULRunner substitution for plain HTML pages (JSF/xhtml still requires XULRunner). The point is that, when XULRunner is unavailable, HTML Preview will be used in "Visual/Source" and "Preview" tabs of the VPE.

Two new JAX-RS wizards now replace the former "Create Sample RESTFul Web Services" wizard:

The JAX-RS Resource creation wizard also allows for JAX-RS Application creation if none already exists in the project. This step can be skipped if the user plans to deploy her project on a non-Java EE platform. A third option, labelled "Skip the JAX-RS Application creation", is displayed on the "JAX-RS Application" dialog page shown above.

The JAX-RS Resource wizard can be invoked from "File>New" in the menu bar and in the project’s menu. It also appears in the Servlet group in the toolbar, both in the Java EE and JBoss perspectives.

Both JAX-RS Resource and Application wizards can be invoked from a selected element in the Project Explorer, including classes, packages, source folders and the "JAX-RS Web Services" node. The default values will depend on the current selection.

The JAX-RS tooling now validates the parameter types in the Resource Methods. In particular, it verifies that the parameter types meet one of the following requirements:

When defining custom NameBinding and HttpMethod annotations, the @Target and @Retention meta-annotations must be set with appropriate values. Not only the JAX-RS Tooling has been recognizing those custom annotations and validating the values of the aforementioned meta-annotations for a while, but it also now provides users with quickfixes to set the expected values from the error marker in the Java editor (and not only from the Markers view).

Tooling for server-side JAX-RS 2.0 development is almost complete (see New and Noteworthy of JBoss Tools 4.2.0.Beta1). The 2 remaining features to implement are:

As-you-type validation occurs in the scope of the java element (type declaration or method) that is being edited. If the java element corresponds to a JAX-RS element, this later is validated. Note that as opposed to "cascade validation" (see below) that occurs when the underlying file is saved, the related JAX-RS elements are not validated "as-you-type", in order to keep the process as fast as possible.

When fixing problems in a class, all related JAX-RS elements are included in the set of classes of to be validated, which means that related problems can end up being resolved too.

For example, let’s assume that a user has the following classes:

and

In this example, the JAX-RS validator will report a problem on the CarResource#createCar(Car) method because the Car class is not a valid parameter: the Car#fromString(String) method should actually be static. When the user adds the missing static modifier on the Car#fromString(String) method and saves the file, not only the Car class will be validated, but also the CarResource, and at the end of the day, the problem reported earlier will be resolved.

JAX-RS Resource Fields and Properties (ie, fields or setter methods annotated with @PathParam, @QueryParam, @MatrixParam), as well as the JAX-RS 2.0 Parameter Aggregators (ie, method parameters, fields or setter methods annotated with @BeanParam) are recognized.

These elements are taken into account when validating the project and when displaying the Endpoints URI templates in the Project explorer.

For example, let’s assume that a user has the following class:

In that case, the Endpoint URI template associated with the Resource Method and displayed in the Project Explorer will be /{id:String};year={String}?color={String}

Now, if the user has the following classes:

and

then the Endpoint URI template associated with the Resource Method (and its associated Parameter Aggregator) and displayed in the Project Explorer will also be /cars/{id:String};year={String}?color={String}

In this second example, it is the @BeanParam annotation on the method parameter that is used to link to the Parameter Aggregator.

JAX-RS 2.0 is part of JavaEE7 and JBoss Tools now provides you with support for this update of the specification.

The JAX-RS Endpoint templates that are displayed in the Project Explorer have been updated: each parameter name in the @Path, @QueryParam and @MatrixParam annotations is followed by its type as shown below: