anchor.diff:  2. Compile the java code and process resources (if any)
   3. Build a _fat-jar_
   
  -A _fat-jar_ (also called _uber_ jar or _shaded_ jar) is a convenient way to package a Vert.x application. It creates a
  +A _fat-jar_ (also called _uber_ jar or _shaded_ jar) is a convenient way to package a Vert.x application. It creates an
   _über-jar_ containing your application and all its dependencies, including Vert.x. Then, to launch it, you just need
  -to use `java -jar ....`, without having to handle the `CLASSPATH`. Wait, I told you that Vert.x does not dictate a
  -type of packaging. It's true, fat jars are convenient, but it's not the only way, you can use plain (not fat) jars,
  +to use `java -jar <jar name>` without having to handle the `CLASSPATH`. Wait, I told you that Vert.x does not dictate a
  +type of packaging. It's true, fat jars are convenient, but they are not the only way. You can use plain (not fat) jars,
   OSGi bundles...
   
   The `pom.xml` file also contains a set of properties used to configure the application:
  
positive.code:     })
  ----
  
  First, it retrieves the message body (1). It's a JSON object, and stores it in the `quotes` map (2).
  ****
  
  #### Task - Implementing a Handler to handle HTTP requests
  
  Now that you have the `quotes`, let's use it to handle HTTP request. The code already creates the HTTP server and
  provides the stream of HTTP requests. The stream emits an item for every HTTP request received by the server. So, you
   need to handle the request and write the response.
  
  
negative.code: 
  ### Verticle
  
  As you may have noticed, the code is structured in 3 `verticles`, but what are these? Verticles are a way to structure
   Vert.x application code. It's not mandatory, but it is quite convenient. A verticle is a chunk of code that is
   deployed on top of a Vert.x instance. A verticle has access to the instance of `vertx` on which it's deployed and
   can deploy other verticles.
  
  Let's open the `GeneratorConfigVerticle` class, and look at the `start` method:
  