Issue #2 Ensuring features are parsed before formatters are initialised #652
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following the discussion in #651 it was suggested that reports should not be created until we know if there are syntax errors.
The formatters that use a URLOutputStream with a file protocol will all create their report files when the factory creates the formatter which at the moment is done when RuntimeOptions are created
I have added a test to demonstrate this and attempted to fix it.
See https://github.com/tmullender/cucumber-jvm/issues/2 for some explanation of the approach