anchor.diff:  * the application configuration file
   
   Once generated, look at the `pom.xml`.
  -You will find the import of the Quarkus BOM, allowing to omit the version on the different {project-name} dependencies.
  +You will find the import of the Quarkus BOM, allowing you to omit the version on the different {project-name} dependencies.
   In addition, you can see the `quarkus-maven-plugin` responsible of the packaging of the application and also providing the development mode.
   
   [source,xml,subs=attributes+]
  
positive.code: == Development Mode
  
  `quarkus:dev` runs Quarkus in development mode. This enables hot deployment with background compilation, which means
  that when you modify your Java files your resource files and refresh your browser these changes will automatically take effect.
  This works too for resource files like the configuration property file.
  Refreshing the browser triggers a scan of the workspace, and if any changes are detected the Java files are recompiled
  and the application is redeployed; your request is then serviced by the redeployed application. If there are any issues
  with compilation or deployment an error page will let you know.
  
  
negative.code: [TIP]
  .Differences with vanilla Jax-RS
  ====
  With Quarkus, there is no need to create an `Application` class. It's supported, but not required. In addition, only one instance
  of the resource is created and not one per request. You can configure this using the different `*Scoped` annotations (`ApplicationScoped`, `RequestScoped`, etc).
  ====
  
  