Bug

• [FORGE-486] - Scaffolding an entity with an enum fails
• [FORGE-490] - Cannot access configuration outside of an active Project context
• [FORGE-491] - REST plugin creates compilation errors when "id" setter is not called "setId()"
• [FORGE-492] - REST facet does not recognize Application class with ApplicationPath annotation
• [FORGE-493] - ServletFacet requires web.xml to detect servlet environment
• [FORGE-497] - EJB facet requires JTA API in POM
• [FORGE-498] - faces setup fails if faces-config.xml already exists
• [FORGE-501] - Faces scaffold creates compilation errors when "id" getter is not called "getId()"
• [FORGE-503] - Erroneous f:convertNumber added
• [FORGE-506] - Ensure all plugins use same style of dependencyManagement
• [FORGE-512] - Scaffold setup should ensure JSF API is installed
• [FORGE-513] - AnnotationImpl.removeValue(String) does nothing
• [FORGE-514] - Scaffold targetDir should be stored from setup
• [FORGE-515] - Scaffold targetDir does not relocate index.html and index.xhtml
• [FORGE-516] - org.jboss.modules.ModuleNotFoundException: Module not found in local module loader
• [FORGE-519] - Cannot execute scaffolding after installing a plugin

Enhancement

• [FORGE-496] - --scaffoldType faces redundant

Feature Request

• [FORGE-213] - Java EE6 Full Project (follows the EE6 full profile)
• [FORGE-305] - Forge should inform users when they are attempting to run on an unsupported JRE version
• [FORGE-458] - Specify prefix or target directory for generated CRUD so as to not clobber existing app
• [FORGE-489] - Should be able to define/specify one or more "plugin directories" from which to load plugins during bootstrap

Task

• [FORGE-337] - Document scaffolding usage, and how to enhance application beyond generated pages