[jira] [Updated] (TINKERPOP-3060) Dependency inconsistency between modules.

["Cole Greer (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TINKERPOP-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cole Greer updated TINKERPOP-3060:
----------------------------------
    Component/s: build-release

> Dependency inconsistency between modules.
> -----------------------------------------
>
>                 Key: TINKERPOP-3060
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-3060
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: build-release
>            Reporter: Wei Zhao
>            Priority: Major
>   Original Estimate: 1m
>  Remaining Estimate: 1m
>
> h3. Problem Desciption
> Currently some modules of Tinkerpop are using the same dependency. However, some of these dependencies' versions are not centrally managed and therefore cause discrepancy.
> I found the following dependencies with different versions in different modules.
> {code:java}
> Dependency org.xerial.snappy:snappy-java:jar has inconsistent versions.
>     Dependency {groupId=org.xerial.snappy, artifactId=snappy-java, version=1.1.8.4}
>         /spark-gremlin
>     Dependency {groupId=org.xerial.snappy, artifactId=snappy-java, version=1.1.8.2}
>         /hadoop-gremlin
> ---------
> Dependency com.fasterxml.jackson.core:jackson-databind:jar has inconsistent versions.
>     Dependency {groupId=com.fasterxml.jackson.core, artifactId=jackson-databind, version=2.15.2}
>         /gremlin-shaded
>     Dependency {groupId=com.fasterxml.jackson.core, artifactId=jackson-databind, version=2.13.5}
>         /spark-gremlin
>         /hadoop-gremlin
> ---------
> {code}
> h3. Possible Outcome:
> This increases the maintenance workload and may lead to dependency conflict for downstream projects. So it's better to align the versions of the dependencies if the discrepancy is not intentional.
> h3. Possible Solution
> Align the versions of the dependencies to ensure consistency and avoid possible conflicts. And if it's possible, manage the versions of the dependencies centrally.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)