Help

The JBoss Tools 3.1 M3 release are now available!

3.1 Milestone 3: The Summer Edition!

Improvements

This time around we got 250+ issues fixed and a couple of new features added over the Summer. As always you can see the major highlights with screenshots in What's New!

Maven

We continue pushing our integration with m2eclipse further. Now if you import an existing pom.xml and that pom.xml has a dependency to Seam artifacts we will enable the Seam tooling on that project. Making it even easier to get started without having to mess with the Eclipse configuration. Going forward we will explore doing the same for JSF, Portlet and other framework dependencies.

Furthermore we added support for using Maven dependencies as a WTP 3.1 Library provider, first for JSF Facets but going forward we will open it more up and allow it for others possibly any facet. Stay tuned for that.

Hibernate

We have improved the Dali JPA integration for Hibernate and the visual diagram of Hibernate mappings. The Dali JPA integration is visible when you have setup your project to use the JPA Facet and chosen to use the Hibernate Platform as opposed to the Generic Platform.

We added more support for Hibernate specific annotations so the JPA Details pane now can be used to edit/view them plus the JPA Validator understands more of Hibernate's added flexibility compared to plain JPA and stop giving false warning/errors. Similarly we added support for projects that uses a custom Naming Strategy for table and columns, again making the JPA Validator aware of the Hibernate specific support correcting the validation concerning missing table and columns.

Visual Page Editor

The visual page editor received updates to its supported component set for Richfaces 3.3.1 and for latest JSTL. It also introduces a new CSS Editing perspective to give easier access to the CSS specific views we have introduced over the last few milestones.

SOA

This release also brings updates to the SOA components in the tools, i.e. we now include jbpm4 tooling in addition to the jbpm3 version, there is an updated Drools 5 plugin, the Smooks plugin have been greatly enhanced and we also provide updated bits of our experimental work with using Eclipse BPMN project together with Riftsaw the new bpmn project at JBoss.

SDK Downloads

Our update site now includes a SDK category which you can use to get the actual plugins + the source code used to build them. This allows you to use the Eclipse PDE development environment and improve individual plugins without having to mess with importing code from JBoss Tools SVN. Making contributions even easier - hint hint!

Initially only a few of our plugins are available as SDK's, but we will add more and more as we go through updating their builds to support for SDK creation.

What's next

In the next milestone you will start to see the effect of some of the not-yet-user visible changes we have been working on over the summer. These includes CDI/JSR-299 (aka WebBeans) support, JSF 2 support, More WTP/Maven integration, Smooks and BPM and the biggest small improvement we are contributing to WTP 3.2, but will be available in JBoss Tools 3 first - better module assembly support for WTP projects.

If you want to get a first hand on the progress for these you can use our nightly build update site. See the links on our download page. We might even Twitter about the progress in there.

Feedback

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!

5 comments:
 
16. Sep 2009, 22:18 CET | Link
Adrian Mitev

Congratulations for the realease and thank you for the hard work!

"and the biggest small improvement we are contributing to WTP 3.2, but will be available in JBoss Tools 3 first - better module assembly support for WTP projects" - does this mean that the wtp projects will include the libraries from the ear directly to the class path and will not use the manifest file.

This what wtp does now is ugly - to use the manifest for classpath settings in EAR applications.

 
17. Sep 2009, 04:35 CET | Link

Until EE5 it was actually the only way to do it without having additional metadata somewhere.

In EE5 this are much less relevant since we get the /lib dirs and in EE6 EJB's are allowed to be in a war.

But unfortunately the automatic pickup from jar's in WTP was far from working, but that is luckily fixed now - if it ain't working for you please let me know ;)

But beyond that what WTP is missing is a way to include artifacts from other projects on a less granular level than a project or a lib. And what we realized is that the WTP core actually has a good framework (Virtual Component) that allows for doing this but it is simply not utilized correctly or not exposed in the UI.

That is what we are trying to help fix - the experimental Module Assembly Page (in project preferences for WTP projects) is the first steps for doing that.

 

--max

 
20. Sep 2009, 01:24 CET | Link
Ray

Great work !

Is there support for Seam 2.2 ? Or is even 2.1 still experimental ?

Ray

 
20. Sep 2009, 15:58 CET | Link
Max

Seam 2.2 always worked - but yes we added support in the components.XML editor for the new things in this release.

And the tech preview tag were removed long time ago :)

 
23. Sep 2009, 20:07 CET | Link
Adrian Mitev

Cool the EAR/lib is working now with WTP 3.1.1!