Use gherkin 5.0.0 #1251
Merged
Use gherkin 5.0.0 #1251
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Summary
Use gherkin 5.0.0
Details
Gherkin 5.0.0 will create an empty pickle for an empty scenario. See: cucumber/gherkin-java@f9a0ef0 However a feature without scenario's still doesn't run any thing. The JUnit test has been updated accordingly.
Motivation and Context
With the release of gherkin 5.0.0 the build broke. Due to some black magic in pax-exam the osgi maven bundles will always try to resolve the latest version unless specific version numbers are used. Upgrading gherkin was the easiest way out.
How Has This Been Tested?
Ran the tests. Fixed the tests.
Types of changes