[
https://issues.apache.org/jira/browse/TINKERPOP-2804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640932#comment-17640932
]
ASF GitHub Bot commented on TINKERPOP-2804:
-------------------------------------------
spmallette opened a new pull request, #1878:
URL: https://github.com/apache/tinkerpop/pull/1878
https://issues.apache.org/jira/browse/TINKERPOP-2804
Taking this approach makes it easier for providers to reference the files
from the classpath, otherwise they likely need to have copies of them on the
local file system which isn't so good. This is a breaking change but it only
affects providers. They will have a minor adjustment to make to their test
infrastructure on upgrade.
VOTE +1
> gherkin feature files should be on the classpath
> ------------------------------------------------
>
> Key: TINKERPOP-2804
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2804
> Project: TinkerPop
> Issue Type: Improvement
> Components: test-suite
> Affects Versions: 3.6.0
> Reporter: pieter martin
> Priority: Minor
>
> Currently implementers needs to access the gherkin features on disc.
> It should be available on the classpath.
> i.e. gremlin-test/features should be inside the jar
> This will allow,
> @CucumberOptions(features = { "classpath:/gremlin-test/features" })
--
This message was sent by Atlassian Jira
(v8.20.10#820010)