On the 28th August, Pete and I will be presenting at the opening of the first JBoss User Group in Denmark.
We will be talking about JBoss Seam, Web Beans and JBoss Tools/Developer Studio.
You can see the full schedule at jbug.dk (in Danish).
Kenneth Christensen and Søren Pedersen who is organizing the event tells me that they only have five seats left so hurry up if you want in on the action.
I noticed that there have been a lot of JBoss Tools related news going on while I were on vacation (maybe I should stay on vacation ?)
And No, this version is not for Eclipse 3.4/Ganymede - it is for Eclipse 3.3/Europa. JBoss Tools 3.0 will target Ganymede; I'll blog about that version later.
JBDS 1.1.0.GA which includes JBoss Tools 2.1.2 is also available now.
Max Katz's from Exadel got his Using JBoss Richfaces with JBoss Developer Studio from JavaOne posted on DZone.
DZone also posted a podcast interview (audio and transcript) with me talking about JBoss Developer Studio
Edem Morny posted instructions on how to get Tomcat 6 working with the Seam support in JBoss Tools on his blog.
Finall, Snjezana Peco from JBoss (JBoss Tools) is working on enabling Profile action for our JBoss AS adapters in JBoss Tools 3, but if you want to know how to do it with any version of JBoss Tools then take a look at this forum post where Snejana explains the steps for enabling TPTP profiling.
Today we are releasing JBoss Tools 2.1.0.GA.
JBoss Tools is a set of plugins that enhances and adds support in Eclipse for JBoss.org projects and related technologies such as JBoss AS, Hibernate, JPA, Seam, jBPM, JSF and more.
Version 2.1 has over 350 fixes, improvements and new features which include faster startup, faster Visual Page Editor,
Find references/declarations for Seam EL, flexible project layouts (e.g. a WTP project is not a requirement anymore), 64-bit Linux support and more.
Read the full details in the New and Noteworthy.
Most users should be able to upgrade without any problems to this version. It is just a drop-in replacement.
It is though required to upgrade to Eclipse 3.3.2 and WTP 2.0.2 to use this release since it includes a set of fixes in the core Eclipse platform.
One known caveat is though that users of Seam 1.x or other projects that has JEE5 jars without descriptors (Seam 2 works fine) it is necessary to use our patch to WTP 2.0.2 if you want WTP deployment to work correctly. See the details here.
I encourage everyone to try out JBoss Tools 2.1 and give us any feedback and contributions on our jira and forum. Your feedback is what will help us improve and extend the next version of JBoss Tools.
A few new features did make it into 2.1.x and you can see those at new and noteworthy.
To upgrade safely to this release please read the following.
Existing Seam projects will work fine in this new release, except EAR projects with an application.xml should be updated to have something like the following modules:
<module> <web> <web-uri>myprj.war</web-uri> <context-root>/myprj</context-root> </web> </module> <module> <ejb>myprj-ejb.jar</ejb> </module> <module> <ejb>jboss-seam.jar</ejb> </module>
..and nothing else. The <java> elements we generated previously are unnecessary and breaks WTP 2.0.2. The details about why that is are in the following.
We are now targeting WTP 2.0.2+Patches to get some of its important bugfixes.
Unfortunately WTP 2.0.2 introduced a bad regression bug concerning deployment and another bug which makes WTP 2.0.2 very rigid about deploying jar's listed in application.xml via <java> or <ejb> tags unless they have xml descriptors (which is not required in JEE 5).
This affects Seam 1.2 projects and any other projects using binary jars with EJB's in them and projects that uses <java> or <ejb> in application.xml for jars without descriptors which is the case for projects created with previous version of JBoss Tools
To get around these various bugs/
features of WTP 2.0.2 we had to do two things:
- application.xml in new Seam projects no longer lists jar's in <java> elements to work with WTP 2.0.2. Besides being more correct and standard compliant it also makes the application.xml much smaller so in overall this is a Good thing. Unfortunately existing JBoss Seam projects that uses <java> in application.xml can run into files not being deployed thus we added a EAR validator that will put warnings/errors on offending elements we know can cause problems and with instructions on how to fix it.
- We provide a cumulative feature patch to WTP 2.0.2 which removes the
rigidnessin WTP with respect to JEE jars without descriptors. It is a hack, but it at least allows JEE 5 compliant jars to work instead of causing a exception stacktraces and random behavior in Eclipse.
We had hoped this rigidness could be removed in an update to WTP 2.x, but that does not seem to happen within a decent time frame so we decided to release the patch on our own. Note: WTP 2.0.2+WTP provided patches will work for most users, but we do recommend running with our patch to avoid publishing issues.
p.s. This version of JBoss Tools (sans the experimental parts) will be available in a JBoss Developer Studio 1.1.0.CR1 for JBDS customers soon.
I recently got invited by Gilles J. Iachelini to join a beer bash in Bern, Switzerland on the 15th April.
It's arranged by the Swiss East Eclipse user group so if you are around and interested in Eclipse and JBoss Tools come and say Hi.
Giles invite reminded me of a few other things I wanted to spread the word about...
I met Gilles while I were at EclipseCon and he were doing an EclEmma tutorial together with Marc R. Hoffman.
EclEmma is really nice Eclipse plugin that makes it ultrasimple to run a normal Java project and get code coverage information via Emma.
But since I mostly develop plugins these days I were more interested in using it with Eclipse which is a pain with any other code coverage tools I have tried.
Luckily Marc showed me a very simple trick to get Emma to do code coverage for any Eclipse plugin.
You basically just add their special EclEmma plugin next to the
org.eclipse.osgi plugin and then run Eclipse with
-Dosgi.framework.extensions=com.mountainminds.eclemma.osgihookThis allows Emma to be used to enhance any classes loaded by Eclipse runtime and here by be able to generate a code coverage html report and Emma session file when Eclipse exit.
The HTML report can be directly viewed in a browser but will not include classes that were not loaded, but if you load the Emma session file with EclEmma you can get those statistics too.
Extremely simple and straightforward.
I hope Marc will integrate this soon into EclEmma so it becomes even easier to run.
You can read the details about this trick on EclEmma website
Another useful plugin comes from our own Rob Stryker which the other day got annoyed when he were debugging four different versions of Eclipse and WTP combinations.
He were being fed up with having to constantly setup the matching plugins and source in the debugger. All the current source-lookup options assumes you point to unpacked sources or single archives. That just does not cut it when it comes to Eclipse which consists of multiple src.zip files spread across multiple directories.
Hence Rob created a sourceprovider that can be added to any Debug launch and then tell it about the root directory of an Eclipse installation and it recursively scans for src.zip files and adds it as a place where Eclipse will look for sources.
A great time saver, also for non-eclipse projects that has many src.zip files.
org.jboss.tools.labs.pde.sourceprovider is available in source form from JBoss Tools svn