Move io.cucumber.core.api.Scenario
to backend implementation
#1760
Milestone
io.cucumber.core.api.Scenario
to backend implementation
#1760
Summary
With the introduction of JPMS modules need to declare their dependencies. Additionally they need to declare which transitive modules their consumers have to depend on via
require transitive
. To keep this structure simple we should remove the need to end users to depend oncucumber-core
.So:
io.cucumber.core.api.Scenario
withio.cucumber.java.Scenario
andio.cucumber.java8.Scenario
TypeRegistry
andTypeRegistryConfigurer
in favor of the@ParameterType
annotation and friends.Expected Behavior
Current Behavior
Possible Solution
Add io.cucumber.core.backend.Scenario and make it extend
io.cucumber.java.Scenario
. This will be the scenario representation that Cucumber uses to it's internal components.Add
io.cucumber.java.Scenario
that extendsio.cucumber.core.api.Scenario
. This will be the scenario representation thecucumber-java
module uses to the end user.Deprecate
io.cucumber.core.api.Scenario
and eventually remove it.The text was updated successfully, but these errors were encountered: