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 2021/03/16 21:19:00 UTC

[jira] [Commented] (TINKERPOP-2460) Change groovy to provided scope in gremlin-driver

    [ https://issues.apache.org/jira/browse/TINKERPOP-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302901#comment-17302901 ] 

Stephen Mallette commented on TINKERPOP-2460:
---------------------------------------------

I realized that we really meant that the dependency should be "optional" and not "provided scope". By optional, we mean that it will not show as a transitive dependency to gremlin-driver and is only necessary for users who intend to do {{JsonBuilder}} serialization in which case they need to include the various groovy dependencies as described in the upgrade documentation.

https://github.com/apache/tinkerpop/commit/9abda9b12a23483e9e222c69f5a831666e98278b

> Change groovy to provided scope in gremlin-driver
> -------------------------------------------------
>
>                 Key: TINKERPOP-2460
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2460
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: driver
>    Affects Versions: 3.5.0
>            Reporter: Stephen Mallette
>            Assignee: Stephen Mallette
>            Priority: Minor
>              Labels: breaking
>             Fix For: 3.5.0
>
>
> The only reason we have a groovy in {{gremlin-driver}} is to support {{JsonBuilder}} serialization which (1) I tend to doubt is even used and (2) isn't a defined type for any other serialization format besides GraphSON. While it would be nice to simply remove it completely, I think it would be better to give it {{provided}} scope and force users who depend on it currently to directly depend on groovy for it. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)