Red Hat

In Relation To Eclipse

In Relation To Eclipse

JBoss Tools 3.1 Final

Posted by    |       |    Tagged as Eclipse JBoss Tools

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!

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!

When we released JBoss Developer Studio 2.1 we also announced its updatesite at which is for all customers to use. If you are a 2.1 user you have been able to use it to update to JBoss Developer Studio 2.1.1 which includes some minor bug fixes.

We also started an Early Access Program for existing customers of JBoss Developer Studio 3, and this is available from using the same credentials as customers use for the updatesite.

This Early Access Program gives customers the chance to try out selected milestone builds for the upcoming JBoss Developer Studio 3 and give feedback on the complete JBoss Developer Studio package and not just on the standalone plugins available through the JBoss Tools project.

At the time of writing the release available from the Early Access is JBoss Developer Studio 3 CR1 which is based on Eclipse 3.5 (Galileo), most of the JBoss Tools 3.1.CR1 plugins and supported 3rd party plugins such as TestNG.

Have fun!

Animating JBoss projects with Gource

Posted by    |       |    Tagged as Eclipse JBoss Tools

Gource is a software version control visualization tool and one of its unique features is that its pretty darn fast and support a multitude of version control systems including SVN.

It took me less than 10 minutes to get it up and running to visualize JBoss Tools and Hibernate svn checkout.

It took a little bit of insomnia to also add in automatic fetching of user images from based on the committer names in the logs and I end up with something like this:

The still shot doesn't really make Gource justice so be sure to check out some of the example videos available from Gource.

If you want to try to run this on your own then here is the script I created for it (tested on cygwin but should work on other *nix variants too).

The Script


  • Gource for your platform
  • (place it in the root directory of Gource)
  • svn
  • curl
  • Python
  • Cygwin (if on windows)

Update the GOURCE_HOME in the following (non-optimized, but working) shell-script and save it to

export GOURCE_HOME=/cygdrive/c/work/products/gource
echo Fetching SVN Log
svn log --verbose --xml > gource-svn.log

echo Convert svn log to gource log
python $GOURCE_HOME/ --filter-dirs gource-svn.log > gource-custom.log

echo Getting unique committers from log and preparing urls
gawk -F\| '{ print $2 }' gource-custom.log > gource-all.txt
sort gource-all.txt | uniq > gource-unique.txt

gawk -F\| '{ print "curl -o " $1 ".png" $1 }' gource-unique.txt > gource-urls.txt

echo Fetching committer images from
mkdir gource-img
cd gource-img
sh ../gource-urls.txt 
echo Removing images for users with errors/missing
grep -l "unexpected error" *.png | xargs -n1 -i rm {}
cd ..

echo Running gource
$GOURCE_HOME/gource --log-format custom --user-image-dir ./gource-img gource-custom.log

Now go into the root of the svn checkout you want to run gource on and run sh and see the magic unfold.

Have fun and if you have a machine with enough diskspace/cpu to record a video, post the link!

Episode 8 of JBoss Asylum is now available.

In this late night episode Emmanuel has a confession concerning clustered Lucene indexes

The news are a compacted version of the massive number of releases did, at least known to us, in December and January

And finally we have Andrew and Aslak dropping in to talk about Embedded AS, ShrinkWrap and Arquillian - all ongoing prototype work to speed up and improve our unit and integration testing with EE application containers.

Both Max and Aslak had issues with their connection during this interview, so the audio quality is not perfect in places but we hope you will enjoy it anyway.

Go get it at The Asylum Episode 8

JBoss Tools 3.1 CR1 released

Posted by    |       |    Tagged as Eclipse JBoss Tools

JBoss Tools 3.1 CR1 have been made available to celebrate the new year!

3.1 Milestone CR1: Happy New Year!

Feedback, Feedback, feedback

With close to 280 issues fixed in this release since the M4 release we are really looking for feedback on this first release candidate to be sure we reach a solid GA - so speak up :)


The improvements are many this time around and since I was on holiday during the M4 release, i'll only be able to cover some of the highlights of both M4 and CR1.

The full details and screenshots are as always available in the New and Noteworthy.

Cocoa support on Snow Leopard

The visual page editor now works on both Carbon and Cocoa 32-bit versions for Snow leopard.

JSF 2 and improved code completion

The visual page editor and our code completion now supports JSF 2 features such as composite components and the new resource lookup rules.

The code completion features now provides completion based on what TLD's and resources are available on your projects classpath instead of from a fixed set data. This means the code completion will pickup basic attributes and tags from new release of Richfaces, ICEFaces etc. where as before you had to wait for an update to JBoss Tools to get that support.

Of course not all information is available in the raw TLD's, so some completion features will still require updates - but much less than before.

The code completion also now show javadoc for methods and information about where the component is from. See the screenshots in New and Noteworthy.

Seam and Hibernate

Seam and Hibernate tooling are now even better integrated allowing them to share the same DTP connection removing the need to keeping connection information uptodate in multiple places.

Deployment via SCP

We've added a SCP Remote Server type that allows you perform deployments via scp/ssh. This makes it easy to deploy to a remote server hosted locally or in the cloud directly from within your IDE using the same tools that works for local deployments. The server supports both deploying exploded or in archived form.

Note, the SCP server is not tied to any specific application platform such as JBoss AS but can be used as a general purpose deployment over SCP.

SOA Tooling

The Smooks editor really grew up this time. Many usability issues have been fixed and we now got the possibility to execute a Smooks test run so you can easily try out the Smooks transformation on your own test data.

ESB deployment and configuration editing has now been updated to also support ESB 4.7 and its new actions.

Both ESB and BPEL are now fully WTP type projects allowing them to work the same way as WAR, EAR and ejb-jar in eclipse.

Filesets for (selected) WTP projects

One of the biggest limiting features of Eclipse WTP is that you do not have much control over how your projects are built, i.e. there is no easy way for including a set of resources from another project such as a set of .xhtml files into your WAR.

We now provide this functionality via the new Module Assembly Page on WTP based projects. This functionality we are already contributing back to WTP 3.2, but we wanted to give you a glimpse of it today on the project types we do, such as BPEL and ESB.


Remember, if you want to ensure that JBoss Tools are useful for you too - leave a comment on this blog or use our forums and/or JIRA or to let us know what you think!

Have fun!

We just published the second episode of JBoss Community Asylum.

This time we sat down with Aaron Walker, a long time JBoss Community member which started his involvement all the way back to JBoss 2. From there on he worked on messaging, drools, hibernate search and others. Aaron also gives his advice on how to get involved with JBoss projects and how he learned to cope with being Brock'ed.

In the short news we touch upon Google summer of code, Beer, Java 5 being end-of-life and more.

Get the episode and see full show notes at Asylum

Daniel Azarov have been busy the last few months improving our Find references and Refactoring support for JSF and Seam Expression Language (EL) references.

During that work Daniel created a few movies showing of the features and they are added to the individual jira's about the subject. I thought it would be nice to also get these shown to a broader audience - so here they are, for you to see.

If you want to try this use the M3 release or nightly builds of JBoss Tools.

Searching/Find references

Standard search (Ctrl+Shift+G) finds method references in EL

By using the standard Find references functionality EL expressions that refer to the method shows up next to java references.


Refactoring Demo - renaming the booking component to cooking. Shows how the rename of a component takes effect in both Java, components.xml, pages.xml and .xhtml files.

Notice how it handles changing default injection to explicit naming, i.e.

@In Booking booking;
needs to be changed to
@In(value\="cooking") booking;
to continue to work.

The following movies show a similar rename, just initiated from the components view instead and an example of what happens for read only files.

Rename Seam Component in Seam Components View

Rename component in read-only files

Renaming of EL variables used in Strings

These are for code that refers to EL inside Strings, for example

log.log("${} did something")
. The demo shows this applied in various locations: java editor xml editor properties editor VPE editor

Have fun!

Just a quick note to inform that JBoss Developer Studio 2.1 are now available from the JBoss CSP and what i'm very happy to announce, it is also available from our new update site.

Official Update Site

Until now upgrading JBoss Developer Studio required a full install, but we can now finally remove that obstacle (at least for 2.x releases).

The update site is from now on the official supported way of upgrading JBoss Developer Studio 2.x.

The site to use when upgrading from 2.0 to 2.1 is available at (customers has or will receive the username/password).

Instructions on how to use it can be found here.

JBoss Enterprise Application Platform 5

The major new functionality in this release is the support for JBoss EAP 5 incl. Seam 2.2. This means you can add the EAP 5 server and start, stop and deploy your applications directly from Developer Studio.

Those who uses EAP 4.x, Developer Studio continues to support previous releases of EAP and any of your JBDS 2.0 projects will also continue to work.

Note, for now we provide only the stand alone JBoss Developer Studio 2.1. You need to install the EAP separately and just use the Installer or the JBoss Server view to add your EAP server.

JBoss Tools 3.0.2

This release contains JBoss Tools 3.0.2 which beyond the changes for EAP 5 and AS 5 support has 47 issues fixed.

Have fun!

Asylum - a podcast about and by the JBoss Community

Posted by    |       |    Tagged as Eclipse JBoss Asylum

A crazy experiment called JBoss Community Asylum is now live via and iTunes.

The idea is to get a podcast focused on the JBoss Community and its projects: news, interviews etc.

The podcast are done by Emmanuel Bernard, Michael Neale and Me.

We welcome any feedback, please leave it as comments on the Asylum blog.

back to top