client builder didn't support properly path with spaces in it.
Partially rolled back changes to CommandRunner: process builder doesn't
support properly classpath which starts with quotes but ends without
like: "c:\program files\x\bin\file.dll";fixtures\testFixtures\another.dll
Runtime supports it only via string. Arrays don't work.
Ensure scenarios invoked from scripts use the ScriptTable class of the calling script
Performance improvement by not using reflection to find constructor on each call
Fix typo found by @viderbit.
Reduce code duplication (and make another method accessible for extension)
Merge branch 'master' of https://github.com/unclebob/fitnesse.git
Restored to match original version from upstrea/master
If command line token was wrapped in double quotes - strip those off. Unit test updated.
Merge pull request #507 from fhoeben/ScenarioCreatesParentScriptClass

Ensure scenarios invoked from scripts use the ScriptTable class of the calling script
Merge pull request #508 from sergebug/master

Modified command Line parser with support for config files with space in the file/folder name i.e. "c:\program files\file name.config"
StackTraceEnricherTest fails under Windows if folder contains spaces

This fixes a problem with this junit test under windows if a folder name
contains a space. In the identified location the space is replaced with
"%20" will classpath has spaces.  This fixes this problem by replacing
all "%20" with a space in the location. As the test already replaces /
and \ one more replacement should not break anything further.
Allow Scenarios with parameterized style but with empty paramter names

This fixes a bug whith parameterized style scenarios where the paramters
have no name like:

|scenario | Division _ _ _ | numerator, denominator, quotient|

Previously this only woked with two spaces between each underscore. The
regex pattern has been fixed to work now with only one space.
SyntaxErrors are now counted in the TestSummary

A table has a syntax error during parsing. I.e. a scenrio without a
name:

|scenario|

Also the table was marked as FAILED the test summary had zero failures.
Three things have been fixed now:
1. instead of FAILED the table is shown as ERROR/EXCEPTION
2. The test summary shows 1 exception
3. The error text which contains HTML is printed correctly (with the
HTML formatting)  in the table
Pass output parameters from a decision table to the implementing scenario

output parameters in a decision table have been ignored in scenarios.
Now they are available.
Merge remote-tracking branch 'upstream/master'
AcceptanceTest: Allow Scenarios with parameterized style but with empty paramter names

1. Simplified documentation of the variable scope.
2. Acceptance test for the below issue:
This fixes a bug whith parameterized style scenarios where the paramters
have no name like:

|scenario | Division _ _ _ | numerator, denominator, quotient|

Previously this only woked with two spaces between each underscore. The
regex pattern has been fixed to work now with only one space.
TestCase: SyntaxErrors are now counted in the TestSummary

Acceptance Test for the below:
A table has a syntax error during parsing. E.g. a scenrio without a
name:

|scenario|

Also the table was marked as FAILED the test summary had zero failures.
Three things have been fixed now:
1. instead of FAILED the table is shown as ERROR/EXCEPTION
2. The test summary shows 1 exception
3. The error text which contains HTML is printed correctly (with the
HTML formatting)  in the table
 Pass output parameters from a decision table to the implementing scenario

Acceptance Test:
output parameters in a decision table have been ignored in scenarios.
Now they are available.
 AcceptanceTest: Allow Scenarios with parameterized style but with empty parameter names

Fixed a typing error which made the test fail