fixes #177

null check for test class in ErrorReportingRunner
fixes #875

Fixes https://github.com/junit-team/junit/issues/875

In versions 4.7 through 4.11 setting up a Timeout @Rule with a value of
0 would result in no timeout. In 4.12 FailOnTimeout switched to using
FutureTask.get(timeout). That method treats non-positive timeouts to
mean "timeout right now".

This fix checks that the timeout value is positive before using it,
and otherwise will wait indefinitely.
Move TestClassTest to package org.junit.runners.model.

It is common to add tests to the same package as the class under test.
Create a class TestWithParameters.

This class keeps the data together that are needed for creating a runner for a single data set of a parameterized test. This makes it also clear, that the computation of the name is not the responsibility of the runner but of the Parameterized class.
Extract BlockJUnit4ClassRunnerWithParameters.

Separate the class from the Parameterized runner. Makes it clear, that it is designed for reuse.
Use a ParametersRunnerFactory for creating the test for a set of parameters.

There's now an explicit component for creating the runner of a single set of parameters. IMHO this is a better extension point than overriding a method.

The factory can be specified by the @UseParametersRunnerFactory
annotation or you can subclass the Parameterized class and provide
the factory to its constructor.
Add the default 'Implementation-*' headers to the manifest

Added headers are:
Implementation-Title:     ${project.name}
Implementation-Version:   ${project.version}
Implementation-Vendor-Id: ${project.groupId}
Implementation-Vendor:    ${project.organization.name}

Related to #878

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
Sorters new classes added.
Merge branch 'master' of https://github.com/fshepherd/junit