cucumber/cucumber-jvm — pull request #704 by brasmusson (2014-04-04 18:23:14+00:00)
Title: Only include executed scenarios and steps from outlines in the JSON output

Do not include the Scenario Outline and Examples given as information before the execution of the instantiated scenarios from the outline. This unified the JSON output from Cucumber-JVM regardless of the feature is executed by the command line runner, the JUnit runner of the TestNG runner. The JUnit runner differs from the other by not sending the Scenario Outline and Examples as information to the formatters before executing the instantiated scenarios from the outline, so this PR only affects the output from the command line runner and the TestNG runner.

That the JSON output currently differs depending on which runner was used is confusing both for users (see for instance [this mailing list post](https://groups.google.com/d/msg/cukes/zM7QfHrBnlI/_fSLDmAowhsJ)), and tool developer (for instance the Jenkins Cucumber Report plugin, see [this discussion on a plugin issue starting here](https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java/issues/51#issuecomment-37534412) or [this discussion on a gherkin issue starting here](https://github.com/cucumber/gherkin/issues/165#issuecomment-35559497)).

Fixes #681 and fixes cucumber/gherkin#299, it most likely fix also any remaining Cucumber-JVM part of cucumber/gherkin#165.