anchor.diff:  The extension `quarkus-container-image-s2i` is using s2i binary builds in order to perform container builds inside the Openshift cluster.
   The idea behind the binary build is that you just upload the the artifact and its dependencies to the cluster and during the build they will be merged to a builder image (defaults to `fabric8/s2i-java`).
   
  -The benefit of this approach, is that it can be combined with Openshifts `DeploymentConfig` that makes it easy to rollout changes to the cluster.
  +The benefit of this approach, is that it can be combined with Openshift's `DeploymentConfig` that makes it easy to rollout changes to the cluster.
   
   To use this image extension, you just need to add the following dependency into your project.
   
  
positive.code: 
  .Container Image
  |====
  | Property                                | Type                            | Description                       | Default Value
  | quarkus.container-image.group           | String                          | The group/repository of the image | The ${user.name}
  | quarkus.container-image.name            | String                          | The name of the image             | The application name
  | quarkus.container-image.tag             | String                          | The tag of the image              | The application version
  | quarkus.container-image.registry        | String                          | The registry to use for pushing   | docker.io
  | quarkus.container-image.username        | String                          | The registry username             |
  | quarkus.container-image.password        | String                          | The registry password             |
  | quarkus.container-image.insecure        | Boolean                         | Flag to allow insecure registries | false
  | quarkus.container-image.execution       | Enumeration (NONE, BUILD, PUSH) | The kind of execution (see below) | NONE
  |====
  
  === Jib Options
  
  On top the the global container image options, the following jib specific options are availble:
  
  .Jib Options
  |====
  | Property                                          | Type                            | Description                                     | Default Value
  | quarkus.container-image-jib.base-jvm-image        | String                          | The base image to use for the jib build         | fabric8/java-alpine-openjdk8-jre
  
negative.code: 
  === Docker Options
  
  On top the the global container image options, the following docker specific options are available:
  
  |====
  | Property                                              | Type                            | Description                                     | Default Value
  | quarkus.container-image-docker.dockerfile-jvm-path    | String                          | Path to the JVM Dockerfile                      | ${project.root}/src/main/docker/Dockerfile.jvm
  