Move @Cucumber.Options annotation to core #549
Assignees
Comments
ghost
assigned 
|
When removing @cucumber. api. android. RunWithCucumber how can I change the location of where the features the glue? |
|
@chiavegatto using the |
|
@chiavegatto This is an open ticket, which means it's something we're planning to do. When it's done the ticket will be closed. |
|
For now the default in cucumber-android is leaving these features within assets\features. And the glue? |
mfellner
added a commit
that referenced
this issue
Sep 6, 2013
# By Aslak Hellesøy (9) and others # Via Dmytro Chyzhykov (2) and others * master: [TestNG] Java Calculator TestNG example project - #579 issue. [Jython] Access to scenario in Before and After hooks. Closes #582. Scenario Outlines: Replace tokens in the names of the generated "Example Scenario"s. Change some remaining Cucumber.Options to CucumberOptions No longer used No longer used master is SNAPSHOT Java Calculator TestNG example project. Enable Wicket example, using HtmlUnitDriver so it runs on Travis. Upgraded maven plugins. is deprecated in favour of . Closes #549 Disable wicket example for now Updated History.md with Android improvements. Ref #547 and #574. Attribution. Fix broken test. Closes #568 Enable wicket example. Removed incorrect comment about cargo requiring Java 7. It does not. (Jetty 9 does, but we're on 8 now). #568 Inherit Information of @Cucumber.Options
|
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.
We currently have
@cucumber.api.junit.Cucumber.Optionsand a similar@cucumber.api.android.RunWithCucumberannotation used for Android.We should deprecate these in favour of a
@cucumber.api.CucumberOptionsannotation that can be used by both the JUnit and Android runner (and possibly others in the future).The text was updated successfully, but these errors were encountered: