anchor.diff:  .Example
   [source,xml]
   ----
  -<entryPoint>
  +<entrypoint>
      <!-- exec form  -->
      <exec>
        <arg>java</arg>
        <arg>-jar</arg>
        <arg>/opt/demo/server.jar</arg>
      </exec>
  -</entryPoint>
  +</entrypoint>
   ----
   
   This can be formulated also more dense with:
  
positive.code: .Example
  [source,xml]
  ----
  <entryPoint>
    <!-- exec form  -->
    <arg>java</arg>
    <arg>-jar</arg>
    <arg>/opt/demo/server.jar</arg>
  </entryPoint>
  ----
  
  
negative.code: 
  
  Using `entrypoint` and `cmd` it is possible to specify the https://docs.docker.com/reference/builder/#entrypoint[entry point]
  or https://docs.docker.com/reference/builder/#cmd[cmd] for a container.
  
  The difference is, that an `entrypoint` is the command that always be executed, with the `cmd` as argument. If no `entrypoint` is provided, it defaults to `/bin/sh -c` so any `cmd` given is executed with a shell. The arguments given to `docker run` are always given as arguments to the
  `entrypoint`, overriding any given `cmd` option. On the other hand if no extra arguments are given to `docker run` the default `cmd` is used as argument to `entrypoint`.
  
  ****
  