You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2017/11/30 16:37:00 UTC
[jira] [Closed] (TINKERPOP-1847) tinkergraph-gremlin dependency on
gremlin-test, bad scope?
[ https://issues.apache.org/jira/browse/TINKERPOP-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette closed TINKERPOP-1847.
---------------------------------------
Resolution: Fixed
Assignee: stephen mallette
Fix Version/s: 3.3.1
Fixed via CTR on https://github.com/apache/tinkerpop/commit/9f874ed676733d4e3a78fa091bc938cc1dfc46cd
> tinkergraph-gremlin dependency on gremlin-test, bad scope?
> ----------------------------------------------------------
>
> Key: TINKERPOP-1847
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1847
> Project: TinkerPop
> Issue Type: Bug
> Components: build-release
> Affects Versions: 3.3.0
> Reporter: Cservenak, Tamas
> Assignee: stephen mallette
> Fix For: 3.3.1
>
>
> This issue would be more a "question" type, sorry if missed the point.
> Question is: tinkergraph-gremlin depends on gremlin-tes, but using maven default scope ("compile"). Is this scope proper?
> Cause gremlin-test pulls in stuff like junit, hamcrest and all the test related things, while if I exclude gremlin-test, at runtime tinkergraph runs just fine.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)