updated parent pom
Fix formatting and spelling mistakes in the documentation.

Highlights:
  - In maven-surefire-plugin/src/site/apt/developing.apt.vm, make sure text is
    not rendered bold.
  - In maven-surefire-plugin/src/site/markdown/newerrorsummary.md, ensure
    proper formatting of the list at the bottom of the page.
  - In maven-surefire-plugin/src/site/site.xml, add link to "Using POJO Tests"
    example.
  - In maven-surefire-report-plugin/src/site/fml/faq.fml, mention that
    upgrading Surefire will resolve the listed known issue.
  - Settle on a consistent title casing for (sub)headings.
  - Synchronize page titles with window titles and menu titles, where sensible.
  - Fix/make consistent italic/bold/monospace typesetting of various terms.
Remove reference to SVN
[SUREFIRE-1069] Typo in alwaysGenerateSurefireReport doc: "Defaulyts"
Remove JUnit4Provider.java.orig.
merge pull request #39
https://github.com/apache/maven-surefire/pull/39
[MNGSITE-152] added license and download links
[MNGSITE-152] added download and license links to plugins
[SUREFIRE-1075] Addresses to documented mailing lists in Maven site dead
modernise Jetty configuration
Add rerunFailingTestsCount option for maven surefire to rerun failing tests immediately after they fail.

When rerunFailingTestsCount is set to a value larger k than 0, a failing test will get re-run
up to k times until it passes. If a test passes in any of its reruns,
the build will be marked as successful and the test will count as a
flake (or flaky test). If it fails all those k times then it will
still be marked as a failed test.

In the console output all the flaky tests will be count as "Flakes:
N". The generated test report XML file is augmented with additional
information, while still being compatible with existing consumers
(such as Jenkins). A flaky test will have <flakyFailure> or/and
<flakyError> under its <testcase> element, to store all the flaky
runs' information (such as output, stackTrace). So existing consumers
will still consider it as a passing test, while potential future
consumers can parse those flaky runs information. A failing test will
still have <failure> or <error> under <testcase>, but all the
subsequent re-run information will be stored under <rerunFailure> or
<rerunError>. So existing consumers will still be able to see it's a
failed test and parse its failure information, and potential future
consumers will be able to get all the flaky runs.

It is implemented by keeping a map between test full class name and a
map between all its test methods and the list of runs. It also takes
into account Fork and Parallel and have them covered by integration
tests.

Currently only supports JUnit4.x
Adjust example page for rerun failing tests to be valid for surefire and failsafe plugin
Remove unused import
Added check for return value of await