Removing maven-junit-plugin as it does not support JUnit 4 and Surefire has parallel testing features.
Merge branch 'master' into no-maven-junit-plugin

Conflicts:
	pom.xml
	test/pom.xml
convenient method to retrieve upstream Run
Merge branch 'master' into no-maven-junit-plugin

Conflicts:
	pom.xml
	test/pom.xml
Some missing sysprops.
Merge branch 'master' into no-maven-junit-plugin

Conflicts:
	test/pom.xml
Do not leave interactiveBreak in committed tests.
Baseline usage of Surefire 2.13.
Enabling reusable forked multithreading (4 threads seems good).
Seems to be roughly a few percent faster than maven-junit-plugin baseline.
Merge branch 'master' into no-maven-junit-plugin

Conflicts:
	pom.xml
Revert changes which broke backwad compatibility based on discussion in jenkins-dev list
Revert javadoc too.
fix a lot of http 404 Not Found on some breadcrumbs such as .../testReport or .../pollingLog
Revert changes in method encode too.
Merge branch 'master' into no-maven-junit-plugin
Merge branch 'master' into no-maven-junit-plugin
systemPropertyVariables preferred to systemProperties and makes for smaller diff.
Merge branch 'master' into no-maven-junit-plugin
JUnit 4 broadly supported; no reason to keep a separate junit4 root just for UseRecipesWithJenkinsRuleTest.
Run Parameter's will now contribute an environment variable for the
target run's display name.

The environment variable will be named <PARAM_NAME>_NAME and will
contain the display name of the target build.