Seam 3.0.0.CR2 released

Posted by    |       Seam

The Seam 3.0 CR2 release is now available for download from the following location:

Download distribution

Reference documentation can be found here:

Reference Docs

While the individual Seam module versions haven't changed for this release, the distribution now includes Seam Forge, the totally new, engineered from the ground up shiny successor to seam-gen.

How many times have you wanted to start a new project in Java EE, but struggled to put all the pieces together? Has the Maven archetype syntax left you scratching your head? Everyone else is talking about Rails, Grails, and Roo, and you're left thinking, I wish it were that easy for me. Well, there's good news: You don't have to leave Java EE just to find a developer tool that makes starting out simple. Seam Forge is heating up Java EE, and is ready to work it into a full-fledged project.

It's also an incremental enhancement tool that lets you to take an existing Java EE projects and safely work-in new functionality. Seam Forge comprehends your entire project, including the abstract structure of the files, and can make intelligent decisions of how and what to change. It also features an extensible plugin system, powerful command-link features and much more.

Whether you want to get your startup going today, or make your big customers happy tomorrow, Seam Forge is a tool you should be looking at.

Follow the getting started steps in the Forge reference documentation to find out how easy it is to create a new Java EE project with Forge.

The Seam 3.0 CR2 release also includes an updated version of the Seam Booking example (what would a Seam release be without it?). Many thanks goes to José Freitas for spending the time to get this example working, and for giving it a refreshing new look.

With the CR2 release out of the way, the Seam team will now be working hard to prepare for the 3.0 Final release, which can be expected by the end of this month. If you discover any issues while using the CR2 release, please let us know by reporting it in JIRA.

Back to top