Red Hat

JBoss Tools 3.1 CR2 is now available for download.

3.1 Milestone CR2: CDI, Less typing and the last polish...

Almost there

The CR1 release kicked a nerve and we saw a spike in feedback and this CR2 is our answer. A lot of bug fixes and even some requested features made it in via the 450+ issues fixed for this release.


As the previous 3.1 releases we are targeting Eclipse 3.5.x, but this time we are highly recommending using Eclipse 3.5.1 and if possible the almost to be released Eclipse 3.5.2 because of important bugfixes in core Eclipse and WTP.

Also if you use the Maven integration then we are now working with the just m2eclipse 0.10 and this require you to uninstall m2eclipse 0.9.x to make it work. You can see more about m2eclipse and installation requirements on m2eclipse team blog.


My favorite improvements this time around are below. To see the full details and screen shots read What's New.

Contexts and Dependency Injection

We now support Contexts and Dependency Injection (CDI/JSR-299) annotations and it works on any Eclipse Java project, you simply need to go to the Configure menu and enable CDI.

When enabled this gives you nice code completion in EL for @Named beans, allows you to easily navigate to @Injection points via Ctrl+Click or use search for references finds all occurrences where a named bean are used and if you have validation enabled on the project the project will be checked for certain errors in your CDI constructs giving you instant feedback. Refactoring of methods on CDI beans will be reflected in EL expressions.

JSF Editing

You no longer need to type the namespace (i.e. f:) to get code completion to complete within a namespace. For example, code completing on <out will now show you all the <h:output* tags. Couple that together with also no longer having to type #{ to get EL code completions in attributes editing of XHTML documents are now much simpler and faster.

If you had problems in CR1 with code completion not working for your tag libraries these issues should now be gone. In CR1 we added JSF 2 support and we also moved to use dynamic scanning of the project classpath for taglib information, ensuring the code completion will be guaranteed to match what your project actually uses. This change occurred in CR1 but caused problems for users that were not used to include taglib information on their classpath at build time. In CR2 we now provide a fallback for static taglib information if we do not find it on the classpath.


Both the hbm.xml wizard and JPA Annotation Generation functionality now shares the same UI and allows you to specify the depth for the class graph to generate mappings for and any changes can easily be previewed before finishing the wizard.

m2eclipse 0.10

The JBoss Tools Maven integration have been updated to use m2eclipse 0.10. Remember to remove your m2eclipse 0.9 installation first!


Portal now identifies GateIn as a portal container allowing you to use the existing Portal wizards with GateIn and EPP.


Creation of ESB actions are now easily done via the New ESB Action Wizard and the ESB Editor now has direct links for creation of actions making it trivial to write custom actions.


As always leave a comment, enter our forums, use our JIRA or visit us on IRC to learn about JBoss Tools and give feedback.

Have fun!

back to top