anchor.diff:  <1> By convention, the deployment module has the `-deployment` suffix (`greeting-deployment`).
   <2> The deployment module depends on the `quarkus-core-deployment` artifact.
   We will see later which dependencies are convenient to add.
  -<3> We add  the `quarkus-extension-processor` to the compiler annotation processors.
  -
  -In addition of the `pom.xml` Maven also created the `org.acme.quarkus.greeting.deployment.GreetingProcessor` class.
  +<3> The deployment module also *must* depend on the runtime module.
  +<4> We add  the `quarkus-extension-processor` to the compiler annotation processors.
  +
  +In addition to the `pom.xml` `create-extension` also generated the `org.acme.quarkus.greeting.deployment.GreetingProcessor` class.
   
   [source, java]
   ----
  
positive.code:         <relativePath>../pom.xml</relativePath>
      </parent>
  
      <artifactId>quarkus-greeting-deployment</artifactId> <!--1-->
      <name>Greeting Extension - Deployment</name>
  
      <properties>
  
negative.code: 
  [NOTE]
  .Disclaimer
  To be sure it's extra clear you don't need an extension to add a Servlet to your application.
  This guide is a simplified example to explain the concepts of extensions development.
  Keep in mind it's not representative of the power of moving things to build time or simplifying the build of native images.
  
  