The final release of JBoss Tools 3.1 is here!

3.1 Final

Update site changes

The update site for the final release is

Users moving from JBoss Tools 3.0 on Eclipse 3.4 to JBoss Tools 3.1 will need to install Eclipse 3.5 and then add the update site. Updating Eclipse major versions just goes easier if you do it like that.


This is the official version of JBoss Tools that will run on and require Eclipse 3.5 (Galileo). When installing you can either use the remote Update Site or download the update site zip from the main Download for offline installation. In both cases you can pick and choose which plugins/features you want to install.

For some features other dependencies are needed. For example Maven integration requires m2eclipse 0.10. We have done what we can to enable the related update sites, but in case you disabled them explicitly you would need to add or enable them manually. If you have problems with the installation see this

New Features overview

You can read the previous release blogs or read the full What's New and Noteworthy to get all the glory details for the changes between JBoss Tools 3.0 to 3.1.

Following is a few of the highlights.

Additional Server and deployment support

Support for JBoss Enterprise Application Platform (EAP) and Enterprise SOA Platform (SOA-P) 5 as well as community JBoss AS 5.x and even AS 6 M1 is supported.

With the Module Assembly Page it is now possible to more finegrained control over the assembly of Web Tools Projects.

We introduced the notion of deploying to SSH enabled hosts allowing for basic remote deployments on the local network or on remote clouds such as Amazon EC2.


Support for JBoss Portal and it's successor GateIn and Enterprise Portal Platform (EPP) have been added.


JSF 2 is now supported as well as JSF 1 w/facelets with many optimization in the performance of the visual page editor.

New features in JSF 2 such as composite components and resource look ups are now supported in the visual page editor and in the (x)html code completion.

A lot of improvements in the code completion and visual presentation have made it now even easier and faster to write JSF components no matter if you are into editing source code or visual previewing.


Seam 2.2 support including improved navigation and refactoring of Seam components together with the improvements in JSF support makes JBoss Tools perfect for Seam development.


Hibernate tooling works with connections configured in DTP and Eclipse Dali making it simpler to share connection settings.

If you have an existing Java model you can now easily get either hbm.xml mappings or JPA annotations generated for this model.

Project Examples

It is now easier to get started using JBoss technology by using the Help > Project Examples menu.

More examples have been added and the import have been enhanced to make it more informative about what runtime platforms and versions it will work on.


Maven users can now easily import their Maven projects with m2eclipse and JBoss Tools Maven integration will configure support for JSF, Maven and Portal development in the IDE.


The Context and Dependency Injection specification is supported by providing code completion for @Named component and all the code completion, open-on navigation and refactoring that was done for Seam also applies to CDI components.


SOA tooling have been extended massively by adding support for BPEL on Riftsaw, ESB projects, jbpm4, Drools 5 and Smooks.

Smooks got its own revamped editor and the other editors have been extended and interlinking between the various SOA editors allowing for easy navigation is in place.

ESB Projects allow for easy creation of ESB esb-service and deployment with instant debugging.

...and more!

Have fun!

10. Mar 2010, 21:15 CET | Link

Creat news, will update immediately!

10. Mar 2010, 21:19 CET | Link
Krasimir Goutcev

Congratulations with a great Job.

10. Mar 2010, 23:02 CET | Link

Fantastic news, the CDI stuff looks great :-)

10. Mar 2010, 23:32 CET | Link

Congrat on this important release for the Java EE 6 adoption

Still have some questions: Why the pure JSF 2.0 and CDI support have not been done directly in the Eclipse 3.6 code based? In June 2010, Eclipse 3.6 will ship with some support for EE 6 (not enough to my taste), and I guess we will have some features there that are duplicated and maybe incompatible: which plugins would really provide the JSF 2.0 support?

Anyway some coordination can be done there and some generic Java EE 6 spec features be donated to the Eclipse side so that the default Eclipse 3.6 will have a superb JSF 2.0 and CDI/Weld support (so that the Java EE 6 users of the GlassFish Reference Implementation can have a decent Eclipse based tooling?



11. Mar 2010, 00:52 CET | Link

I think it hard to done smth on Eclipse 3.6 based, when the 3.6 hasn't been released yet. For JSF 2.0 support we provide our own plugins. I don't think that some jsf2 features will be incopatible with eclipse, may be dublicated.

11. Mar 2010, 01:25 CET | Link

Why isn't JSF2 and CDI done directly in Eclipse 3.6 ? Because we only have limited resources and because we support Facelets and uses a different view technology than Eclipse 3.5 and 3.6 limited JSF support. If someone want to give a helping hand please show up on or forum or jira and we would love to help where we can.

btw. We will move to Eclipse 3.6 for nightly builds as soon as we can (probably shortly after EclipseCon) to see what needs doing.

About Glassfish ref impl then im not sure why that requires our JSF2 and CDI support to be in Eclipse ? Our JSF and CDI support is not tied to JBoss.



11. Mar 2010, 01:27 CET | Link

Maxim, I think Ludovic's point is that he want us to contribute to WTP JSF support before 3.6 gets released - which is what I would like to see eventually too; but that is hard to do because of different release cycles, technical differences and the number of hands available to do it ;)



11. Mar 2010, 02:00 CET | Link

Max: I understand it is not easy to coordinate multiple releases with changing technologies (EE 6, Eclipse, JBoss).

I'll be at EclipseCon, and maybe we should touch base and see what can be done (or not) for some synergy for June 2010 or December 2010. I think my new colleagues from Oracle working on JSF 2.0 tooling will be there as well. I am willing to spend time on this topic

Yes, the GlassFish plugin adaptor should work with JBoss Tools plugins as well, maybe with some manual twicks to register the taglib.xml files for EL code completion? A better CDI support in all the Eclipse distros will help the adoption of these new APIs that are so nice!!!

M2Eclipse latest version has also all the Java EE 6 api jars (stripped) so it is also very easy to create maven projects with these apis.

11. Mar 2010, 03:05 CET | Link

Yes let's talk! Alex and maxim will also be at eclipsecon so we can figure something out :)

12. Mar 2010, 00:58 CET | Link

I downloaded the final. I just could not find JSF 2.0 project support.

JSF environment in New JSF Project wizard lists JSF 1.2, JSF 1.2 with Facelets. Where is the JSF 2.0 support as you mentioned?


15. Mar 2010, 09:40 CET | Link
Unfortunately XULRunner for (osgi.os=macosx)( is not ready yet :(
15. Mar 2010, 12:34 CET | Link

What do you mean ? Sure it is. You have any problems ?

15. Mar 2010, 17:19 CET | Link

Unfortunately XULRunner for macosx cocoa is not ready yet :( Why you think so? It's ready, but only x86 version, x86-64 isn't ready.

17. Mar 2010, 16:31 CET | Link

Where is the JSF 2.0 project support ? I tried the latest JBoss Tools 3.1 with eclipse-jee-galileo-SR2 on linux 64b and I can't found anything regarding the JSF 2.0.


23. Mar 2010, 16:14 CET | Link
I'am sorry I mean for x86-64. Does anybody know when it will be ready for x86-64 mac os x?
23. Mar 2010, 23:37 CET | Link
I'am sorry I mean for x86-64. Does anybody know when it will be ready for x86-64 mac os x?

It already run on x86-64, but just in 32-bit mode.

For native 64 bit it will be available the day that we can get a build of Eclipse swt xpcom integration.



22. Sep 2010, 20:27 CET | Link

Is support for JBoss ESB 4.8 included?

Post Comment