anchor.diff:  [[running-tests-build-maven]]
   ==== Maven
   
  -NOTE: The custom `junit-platform-surefire-provider`, which was originally developed by the JUnit team, has been deprecated and is scheduled to be removed in JUnit Platform 1.4. Please use the Maven Surefire's native support instead.
  -
  -Starting with https://issues.apache.org/jira/browse/SUREFIRE-1330[version 2.22.0],
  -Maven Surefire provides
  +NOTE: The custom `junit-platform-surefire-provider`, which was originally developed by
  +the JUnit team, has been deprecated and is scheduled to be removed in JUnit Platform 1.4.
  +Please use Maven Surefire's native support instead.
  +
  +Starting with https://issues.apache.org/jira/browse/SUREFIRE-1330[version 2.22.0], Maven
  +Surefire provides
   http://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-platform.html[native support]
   for executing tests on the JUnit Platform. The `pom.xml` file in the
  -`{junit5-jupiter-starter-maven}` project demonstrates how to it and can serve as a
  +`{junit5-jupiter-starter-maven}` project demonstrates how to use it and can serve as a
   starting point for configuring your Maven build.
   
   [[running-tests-build-maven-engines-configure]]
  
positive.code: In order to have Maven Surefire run any tests at all, at least one `TestEngine`
  implementation must be added to the test classpath.
  
  To configure support for JUnit Jupiter based tests, configure a `test` dependency on the
  JUnit Jupiter API and the JUnit Jupiter `TestEngine` implementation.
  
  [source,xml,indent=0]
  [subs=attributes+]
  
negative.code: 
  Note, however, that you can override this default behavior by configuring explicit
  `include` and `exclude` rules in your `pom.xml` file. For example, to keep Maven Surefire
  from excluding static member classes, you can override its exclude rules as follows.
  
  [source,xml,indent=0]
  [subs=attributes+]
  