anchor.diff:  ----
   
   This will compile the code and run the unit tests included within the generated project.
  -Unit testing is the same as any other Java project and does not require running on Amazon.  Quarkus dev-mode is also
  +Unit testing is the same as any other Java project and does not require running on Amazon.  Quarkus dev mode is also
   available with this extension.
   
  -If you want to build for native too, make sure you have GraalVM installed correctly and just add a `native` property
  +If you want to build a native executable, make sure you have GraalVM installed correctly and just add a `native` property
   to the build
   
   [source,bash,subs=attributes+]
  
positive.code: ./mvnw clean install -Dnative
  ----
  
  NOTE: If you are building on a non-Linux system, you will need to also pass in a property instructing quarkus to use a docker build as Amazon
  Lambda requires linux binaries.  You can do this by passing this property to your Maven build:
  `-Dnative-image.docker-build=true`, or for Gradle: `--docker-build=true`.  This requires you to have docker installed locally, however.
  
  [source,bash,subs=attributes+]
  ----
  ./mvnw clean install -Dnative -Dnative-image.docker-build=true
  ----
  
  == Extra Build Generated Files
  
  After you run the build, there are a few extra files generated by the quarkus lambda extension you are using.  These files
  are in the the build directory:  `target/` for maven, `build/` for gradle.
  
  * `function.zip` - lambda deployment file
  * `sam.jvm.yaml` - sam cli deployment script
  
negative.code: (if you are deploying an AWS Gateway HTTP API) or the `quarkus-amazon-lambda-rest` extension (if you are deploy an AWS Gateway REST API).
  These extensions automatically generate everything you might need for your lambda deployment.
  
  Also, at least in the generated Maven archetype `pom.xml`, the `quarkus-resteasy`, `quarkus-vertx-web`, and `quarkus-undertow`
  dependencies are all optional.  Pick which HTTP framework(s) you want to use (JAX-RS, Vertx Web, and/or Servlet) and
  remove the other dependencies to shrink your deployment.
  
  === Examine sam.yaml
  