]
Lincoln Baxter III closed FORGE-1785.
-------------------------------------
Assignee: Vineet Reynolds
Fix Version/s: 2.6.0.Final
(was: 2.x Future)
Resolution: Done
Explicitly setup in scaffolding, not in Bean Validation nor in JPA
------------------------------------------------------------------
Key: FORGE-1785
URL:
https://issues.jboss.org/browse/FORGE-1785
Project: Forge
Issue Type: Enhancement
Components: Scaffold
Affects Versions: 2.5.0.Final
Reporter: Antonio Goncalves
Assignee: Vineet Reynolds
Fix For: 2.6.0.Final
By now, most of the {{setup}} commands are optional (see [FORGE-1686] or [FORGE-1479]).
Forge takes the setup by default if not specified. Same should happen with scaffolding.
Today, to scaffold a JSF application, we need to execute :
{code}
scaffold-setup
scaffold-generate --targets org.test.model.* ;
{code}
It would be better if, following the same principals, the setup command would run as a
default, and only this would be needed :
{code}
scaffold-generate --targets org.test.model.* ;
{code}
If we want to explicitelly scaffold an AngularJS app, then we would go :
{code}
scaffold-setup --provider AngularJS ;
scaffold-generate --targets org.test.model.* ;
{code}