Closed DemianTinkiel closed 6 years ago
We're in the process of migrating all cucumbers to gherkin3, where this problem will not occur.
We're not likely to fix the bug in gherkin2 (this repo).
I don't have an ETA for when cucumber-jvm will use gherkin3, but we're working on it.
I understand. Thanks for letting me know. Would you have a workaround? On 13 Nov 2015 9:07 pm, "Aslak Hellesøy" notifications@github.com wrote:
We're in the process of migrating all cucumbers to gherkin3 https://github.com/cucumber/gherkin3, where this problem will not occur.
We're not likely to fix the bug in gherkin2 (this repo).
I don't have an ETA for when cucumber-jvm will use gherkin3, but we're working on it.
— Reply to this email directly or view it on GitHub https://github.com/cucumber/gherkin/issues/341#issuecomment-156557062.
Would you have a workaround?
Don't use a colon in your tags ;-)
@aslakhellesoy Hi, I get stuck on this issue recently. I find it still exists on cucumber-jvm 1.2.4. Which release uses gherkin3 as you had mentioned? Should we upgrade to cucumber 2 to solve this problem?
Cucumber-JVM 1.2.4 is 2.5 years old. We won't make any more releases to the 1.2 series.
Please upgrade to 2.x
I have a feature file annotated as
When I run
I get