anchor.diff:  <1> org.eclipse.microprofile.jwt:microprofile-jwt-auth-tck is the MP-JWT artifact
   that contains the base `LoadableExtension` and `ApplicationArchiveProcessor` classes,
   as well as the `ITokenParser` harness factory interface and `TokenUtils` class.
  -<2> The 2 indicated Arquillian extension SPI dependencies provide the
  +<2> org.eclipse.microprofile.jwt:microprofile-jwt-auth-tck type=test-jar is the MP-JWT
  +TCK tests themselves you need to run for the TCK. You would only need this if you are
  +running the TCK from within your TCK harness project.
  +<3> The 2 indicated Arquillian extension SPI dependencies provide the
   `LoadableExtension` and `ApplicationArchiveProcessor` interfaces and dependent
   classes.
  -<3> The TCK unit tests make use of the JAX-RS client API, but do not provide an
  +<4> The TCK unit tests make use of the JAX-RS client API, but do not provide an
   implementation, so your TCK harness artifact must specify what implementation to use.
   Here the Resteasy implementation is being specified.
  -<4> Lastly, you must specify the property Arquillian container runtime that is
  +<5> Lastly, you must specify the property Arquillian container runtime that is
   approriate for you MP-JWT implementation, along with whatever container
   runtime dependencies are required.
   
  
positive.code:             <artifactId>microprofile-jwt-auth-tck</artifactId>
              <version>1.0-SNAPSHOT</version>
          </dependency>
          <!-- Arquillian extension SPI --><2>
          <dependency>
              <groupId>org.jboss.arquillian.container</groupId>
              <artifactId>arquillian-container-spi</artifactId>
  
negative.code:         </dependency>
  
          <!-- Specify your container runtime arquillian integration and dependencies -->
          <dependency><5>
              <groupId>MY_GROUP</groupId>
              <artifactId>arquillian-container</artifactId>
              <version>${container-version}</version>
  