anchor.diff:  
   This command has several effects. First of all, it has created a `persistence.xml` file in the right place (under the `META-INF` directory) with all the default configuration for Hibernate. Then, it has created a `Book` entity under the subpackage `model`. Notice that this entity already has an `id` and `version` with its getters/setters. As you can see, the good thing with Forge is that with only one command all is setup and ready to go. 
   
  -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.
  +If you do not wish to use the Java EE container default data-source, you can also specify additional connection options 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.
   
   [source, console]
   ----
  
positive.code: 
  ==== CLI
  
  To create a new JPA entity, let's use the `jpa-new-entity` command : 
  
  [source, console]
  ----
  
negative.code: [Book.java]$ constraint-add --onProperty description --constraint Size --max 3000
  ----
  
  Behind the scenes Forge as created a `validation.xml` file, added the Bean Validation dependency and the needed constraints. If you want to take a glance at the code, and see a summary of progress, you can use the `more` command or even `ls` your class :
  
  [source, console]
  ----
  