[forge-dev] Forge 2.4.1.Final Released

JBoss Forge 2.4.1.Final is now available!

The Forge Team is proud to announce that JBoss Forge 2.4.1.Final is now available! This is the best release so far. What’s new and noteworthy?

• Performance : We have introduced some major performance enhancements in the Furnace runtime, so the shell and other features should feel quite a bit snappier. Try it out and tell us your thoughts!

• Component Upgrades : We’ve upgraded to Arquillian 1.1.4.Final, Aesh 0.52 and Roaster 2.1.0.Final. More stability and new features available out-of-the-box

• Introducing Roaster (definitely) : Our first-gen Java parser has been replaced by Roaster , which has been refactored and enhanced to support lots of new features such as Nested Types, Java Properties, and more.

And that’s not all! Check out the issues below for more info.

Please let us know if you encounter any issues, or have any feedback on usability, at http://issues.jboss.org/browse/ FORGE . Download Forge

• Try out Forge 2 in Eclipse via our Update Site

• Use Forge 2 in your CLI / Terminal by downloading and installing the Final release . You can learn how to run the downloaded installation via our docs.

Release Notes – 32 issues were resolved since the last release. Check out all the new stuff!

Bug

• – Forge should add EJB 3.1 dependency

• – Freemarker includes present in the classpath are not resolved.

• – REST resource generation fails when DTOs are generated

• – Adding constraint with regular expression throws an Error

• – JavaClass.getProperties() returns wrong number of items

• – Errors in PlexusContainer inutilizes shell

• – ClassCastException when a wizard is invoked in Eclipse plugin

• – CCE when starting up the integrated Forge console in JBT

• – No commands are displayed sporadically

Component Upgrade

• – Upgrade to Arquillian 1.1.4.Final

• – Upgrade to Aesh 0.52

• – Upgrade to Roaster 2.1.0.Final

Enhancement

• – Selection of page template is both unclear, and too prominently displayed in Scaffold Setup in Eclipse

• – Highlighter Scanners should be more extensible

• – Move the utility classes from the scaffold-api project to a scaffold-spi project

• – MavenJavaCompilerFacet should use user properties instead of declaring the compiler plugin

• – Migrate Property used in Validation/constraint support in JavaEE to Roaster

• – Property should extend AnnotationTarget

• – Use Roaster in the JavaEE addon instead of java-parser

Feature Request

• – java new-field improvements

• – Install addon from git repository

• – Extend the Highlighter for Properties files

• – Port the MetawidgetInspectorFacade API from the Forge 1 scaffold-x API

• – Add highlighter for SQL

• – Add Highlighter for Groovy

• – Add Highlighter for YAML

• – Create a ProjectType for a POM packaging type project

• – Implement possibility to add CommandExecutionHandler to ShellHandle

• – Remove java-parser in favor of Roaster

• – Shell does not display execution progress through UIProgressMonitor

Quality Risk

• – High CPU consumption on Windows and Linux

Task

• – Move git addon to core