Skip navigation

We got our first developer milestone build for JBoss Tools which targets Eclipse 3.6/Helios.


[Download] [Update Site]  [What's New] [Movies] [Documentation (not updated yet)]  [Forums]  [JIRA] [Twitter]


Eclipse 3.6/Helios & Java 5

This release is the first milestone that targets Eclipse 3.6/Helios. This means you should only use this with Eclipse 3.6; if you want to stay on Eclipse 3.5 continue to use JBoss Tools 3.1.


Some plugins might still work, but by default the target is Eclipse 3.6.


We also moved our Target Java platform to Java 5 thus if you are still running Java 1.4 on your desktop it is time to upgrade.


Please be aware there a two major known issues with Eclipse 3.5.0, see the "Known Issues" section if you are having problems.

100% Tycho Build

This release of the plugins is the first  release that uses Maven with the Tycho plugin to build and package the  plugin distribution.

Tycho still has its quirks but the quirks are  far far less than "Good'old" PDE Build; we plan to do even faster  release cycles/builds in the future and using Tycho is a major part of  this.

New Features Overview

This milestone covers beyond the Eclipse 3.6 migration and integration new features across the board. The highlights for this release for me is:

JPA 2 Support

Hibernate Tools integration with Eclipse JPA/Dali now supports JPA 2 tooling.

JSF 2 Quick fixes and refactoring

Writing and editing JSF 2 Composite components becomes much easier in this release with quick fixes for missing attributes or folders to composite components and even refactoring of attribute names gets reflected in the interface component section.

Externalize Strings for XHTML

If you know the externalize strings in Eclipse for Java code then you know how the Externalize Strings for XHTML works.

It allows you to select a string, choose externalize String and JBoss Tools will take care of creating the resource bundle if necessary, give it a name and replace the string with the apropriate EL expression. This makes it easier to do internationalization(i18n).


This is a feature we have been asked for a few times thus we are very much interested in hearing feedback on how it works for you.

CDI Wizards and Validation

There are now wizards to create the common annotation types in CDI such as Qualifiers, Sterotypes, Scope and Interceptor Binding.

The validation of CDI constructs have also been further expanded, covering about 60 TCK based validations giving developers an early warning if things are not correctly wired up in the sourcecode.

jBPM 3 Deployment

The deployment mechanism for jBPM within the plugin have been revamped to be more consistent and userfriendly. Removing the need to type too much manually and giving better freedom for how processes can be stored and structured. i.e. before one directory could only have one process, it can now have multiple.

JAX-WS and "Rest" Webservice Tester

Finally but definitly not least is the new "Webservice Tester" which allows you to very easily directly from within Eclipse perform JAX-WS requests or basic "Rest" style requests (read: basic HTTP operations) and inspect the result. If you found the WTP provided Web Service explorer too limited and found other Web Service plugins too complex/heavyweight to install use then give this a try - it's nice and simple.


That were my current highlights, alot of other things were done for this release together with a good set of bugfixes. You can view more details about the above including screenshots on the What's New page.


Known Issues

Unfortunately there are two known issues in Eclipse 3.6.0 and Web Tools 3.2.0 that is affecting JBoss Tools (and many other eclipse plugins) you should be aware of before installing Eclipse 3.6.


If you use Oracle (previously Sun) Java SDK 6 Update 21, then be aware you have to manually specify permgen when starting Eclipse since otherwise you will quickly get an out of memory exception or related error because of this Eclipse bug. Note, any previous Oracle/Sun JDK will work fine, it is only Java 6 Update 21 that is causing problems.


Workaround is to start eclipse with explicit memory arguments, i.e. eclipse -vmargs -Xms256m -Xmx1024m -XX:MaxPermSize=256m


The Web Tools issue is deployment and management of WTP Servers can be very slow for projects with high number of files because of a bug in Eclipse WTP.


Both of these bug is set to be fixed in the soon to be released Eclipse SDK 3.6.1 and WTP 3.2.1.

What's Next ?

The next release (3.2.0.M2) is already being built on and are available in the nightly builds; you can already start using these if you want to and follow the jira and forums for details.


As always feedback is welcome and we look forward to hear your input and other contributions.


Have Fun!

Andre D. wrote a nice Wiki outlining how to use Google GWT Plugin together with JBoss Tools


It is all done by simply using JBoss Tools Project Archives to package up the relavant War and

there by be able to publish to any of the JBoss AS server adapters all without requiring

moving to Eclipse WTP projects.


It's great to see that our good old Project Archive functionallity can still be put to good use.


We are working on seeing how to get Google GWT Plugin work more integrated with the

remainder of the Eclipse ecosystem, especially in context of being able to use GWT without

fuzz as a Facet on Eclipse WTP based projects allowing the full power of WTP to be used

on GWT based projects.

Yes, I'm back again... And this time, it's a bit of a beautification process we've put the Web Service Tester through...


We did some spring (well, summer now) cleaning to wipe away the ugly gray backgrounds and dreary boxes. In their place, we have the gleaming white controls and clean lines available using the Eclipse Forms Toolkit.


Here's an example after invoking a JAX-WS service.


You'll notice we've pared down a few things.


  1. We got rid of the Action URL, since usually you won't need that if you're testing from a WSDL (which is one of our two primary use cases).
  2. We combined the two combo boxes into one - so if you're doing a JAX-WS invocation, you select "JAX-WS" in the list and if you're doing a JAX-RS call, you specify the operation - GET, POST, PUT, and DELETE.
  3. Instead of big textual buttons, we went with smaller toolbar-style buttons with icons and tooltips. The two in the top right are for selecting a WSDL and invoking the service. The four in the Response Body section are: Save to File, Open in Editor (XML or Text), Show Raw Text, and Show in Web Browser. The last is handy if your web service (specifically some RESTful services) return formatted HTML.
  4. And instead of tabs, we went with collapsible sections.
  5. Like before, we have a resizable sash between the Request and Response sections of the view. However, I'm debating adding another sash on the right side between the Request Headers and Request Body areas to aid in resizing that a bit more.
  6. We got rid of the connection to the TCP/IP Monitor simply because it was redundant. If you have a call for that functionality, we can look at adding it back in, but we thought it was a bit of overkill. at this point.


Here's an example after executing a JAX-RS service's GET call with the response body opened in an editor above it:


So all in all, I'm quite pleased with the results of this "facelift". It should start appearing in builds for the JBoss Tools 3.2 M2 milestone soon, so let me know what you think when you play with it.



JBoss Tools tycho build now provides code coverage report for eclipse-test-plugins. All eclipse-test-plugin pom.xml files provide meta information about what bundles are instrumented and what classes are included in coverage report through properties:

  • emma.filter - emma filter to define what packages to include to or to exclude from report
  • emma.instrument.bundles - comma separated list of bundles to be instrumented on the fly during tests execution


Here is an example from plug-ins




To enable code coverage report generation during build




system property should be added to build command line. It activates maven coverage profile to generate coverage reports on per test plug-in basis in text and xml formats. Text reports are printed out to the build console output like


     [echo] [EMMA v2.0.5312 report, generated Wed Jul 07 12:11:50 PDT 2010]
     [echo] -------------------------------------------------------------------------------
     [echo] [class, %]     [method, %]     [block, %]     [line, %]     [name]
     [echo] 61%  (22/36)!     28%  (93/328)!     17%  (1056/6326)!     20%  (308.2/1575)!     all classes
     [echo] total packages:     8
     [echo] total classes:     36
     [echo] total methods:     328
     [echo] total executable files:     28
     [echo] total executable lines:     1575
     [echo] [class, %]     [method, %]     [block, %]     [line, %]     [name]
     [echo] 0%   (0/1)!     0%   (0/7)!     0%   (0/78)!     0%   (0/16)!
     [echo] 0%   (0/2)!     0%   (0/40)!     0%   (0/492)!     0%   (0/125)!
     [echo] 17%  (1/6)!     4%   (3/77)!     4%   (92/2401)!     4%   (24.9/562)!
     [echo] 67%  (4/6)!     35%  (11/31)!     19%  (77/396)!     23%  (23.2/102)!
     [echo] 75%  (6/8)!     33%  (25/75)!     21%  (367/1734)!     24%  (99.2/419)!
     [echo] 75%  (3/4)!     48%  (11/23)!     24%  (135/562)!     32%  (44.1/139)!
     [echo] 75%  (3/4)!     42%  (23/55)!     36%  (153/422)!     36%  (52.4/144)!
     [echo] 100% (5/5)     100% (20/20)     96%  (232/241)     95%  (64.4/68)
     [echo] -------------------------------------------------------------------------------


Reports are generated to /target/emma folder of test plug-in.


To enable code coverage for your test plug-in just add properties listed above to your plug-in pom.xml file and activate coverage profile as it explained above.

I needed to make some suggestions to the new Webservice testing functionallity bfitzpat is Using the RESTeasy Project Example and the WS Tester.




I wanted to use my little SWT to Balsamiq spy but it turned out this view used a couple of components the "Spy" did not understand,

i.e. TabFolder instead of CTabFolder and others.


I had to fix that, so now contains an updated version which allows me to get a good mockup of the above.


Beyond supporting more components it also now ask's you if you want the full workbench converted into Mockup or

just the current View/Editor.



And finally it stopped exporting unknown controls which caused Balsamiq to show an error dialog per unknown component.

Now it just gets ignored. Much easier.


Hope you like it.

Update: There is now a final version of JBoss Tools for Helios! No need to use the nightly builds unless you want to live on the bleeding edge!

For those who are trying to run JBoss Tools on Eclipse 3.6 aka Helios then we are working on getting a M1 build out, but for those

eager to use Helios the nightly builds can help you.


We recommend you use the update site over any of the separate standalone zip builds, thus either use the updatesite ( or the update site zip from the nightly zip builds.


Don't forget to let us know if you find something not working as you expect. You can do so in our jira

or discuss them in the forums


Have fun!