anchor.diff:  
   As you can see, Forge has a all set of parameters to quickly create attributes and customize their JPA mapping. Now let's say we want to specify that a book is written in a certain language. We can use Forge to quickly create a Java enum and then have it as a JPA Enumerated in the `Book` entity :
   
  -[code, script]
  +[code, console]
   ----
   [Book.java]$ java-new-enum --named Language --targetPackage org.cdbookstore.model
   [Language.java]$ java-new-enum-const ENGLISH
  
positive.code: 
  By default Forge scaffolds a web application with JSF 2.0 but you can change this configuration by executing the `faces-setup` command. In fact, most of the Forge commands can be setup (e.g. `jpa-setup`, `servlet-setup`...)
  
  [code, script]
  ----
  $ faces-setup --facesVersion 2.2
  ----
  
negative.code: 
  If you do not wish to use the Java EE container default data-source, you can also specify additional connection parameters such as JNDI data-source names, JDBC connection information, and data-source types. Note, however, that this means you will probably need configure your application server to provide this new data-source and/or database connection.
  
  [code, console]
  ----
  [cdbookstore]$ jpa-setup --provider Eclipse Link --dbType POSTGRES --dataSourceName java:comp/DefaultDataSource
  ----
  
  Then, let's create a few fields. Again, one single command end Forge will do its best to simplify our lives :
  
  [code, console]
  ----
  [Book.java]$ jpa-new-field --named title
  ----
  
  This creates an attribute called `title` of type `String` with get/set methods. Notice that Forge has also updated the `toString` method. Let's add more commands with different parameters (remember to press `TAB` to get the parameters) :
  
  [code, console]
  ----
  [Book.java]$ jpa-new-field --named description --length 2000
  [Book.java]$ jpa-new-field --named price --type java.lang.Float
  