anchor.diff:              </run>
           </groups>
           <classes>
  -            <class name="org.eclipse.microprofile.jwt.tck.parsing.TokenValidationTest" />
               <class name="org.eclipse.microprofile.jwt.tck.util.TokenUtilsTest" />
  -            <class name="org.eclipse.microprofile.jwt.tck.parsing.TestTokenClaimTypesTest" />
               <class name="org.eclipse.microprofile.jwt.tck.container.jaxrs.UnsecuredPingTest" />
               <class name="org.eclipse.microprofile.jwt.tck.container.jaxrs.RequiredClaimsTest" />
               <class name="org.eclipse.microprofile.jwt.tck.container.jaxrs.ClaimValueInjectionTest" />
  
positive.code: </project>
  ----
  <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> 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.
  
negative.code: == Running Your Implementation With the TCK
  Once you have built and installed your TCK harness artifact, you can run the
  TCK tests against it by using either the `tokens-se` or `container` profiles.
  
  === container Profile
  The container profile is a test of JAX-RS client tests that validate a JAX-RS endpoint bundled in a WebArchive deployment
  