[
https://issues.apache.org/jira/browse/TINKERPOP-3060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhao updated TINKERPOP-3060:
--------------------------------
Description:
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.
```
Dependency com.google.guava:guava:jar has inconsistent versions between modules.
Dependency {groupId=com.google.guava, artifactId=guava, version=31.1-jre,
type=jar}
/gremlin-annotations
Dependency {groupId=com.google.guava, artifactId=guava, version=27.0-jre,
type=jar}
/spark-gremlin
/hadoop-gremlin
---------
Dependency org.xerial.snappy:snappy-java:jar has inconsistent versions between
modules.
Dependency {groupId=org.xerial.snappy, artifactId=snappy-java,
version=1.1.8.4, type=jar}
/spark-gremlin
Dependency {groupId=org.xerial.snappy, artifactId=snappy-java,
version=1.1.8.2, type=jar}
/hadoop-gremlin
---------
Dependency com.fasterxml.jackson.core:jackson-databind:jar has inconsistent
versions between modules.
Dependency {groupId=com.fasterxml.jackson.core,
artifactId=jackson-databind, version=2.15.2, type=jar}
/gremlin-shaded
Dependency {groupId=com.fasterxml.jackson.core,
artifactId=jackson-databind, version=2.13.5, type=jar}
/spark-gremlin
/hadoop-gremlin
---------
```
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.
was:
# 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.
```
Dependency com.google.guava:guava:jar has inconsistent versions between modules.
Dependency {groupId=com.google.guava, artifactId=guava, version=31.1-jre,
type=jar}
/gremlin-annotations
Dependency {groupId=com.google.guava, artifactId=guava, version=27.0-jre,
type=jar}
/spark-gremlin
/hadoop-gremlin
---------
Dependency org.xerial.snappy:snappy-java:jar has inconsistent versions between
modules.
Dependency {groupId=org.xerial.snappy, artifactId=snappy-java,
version=1.1.8.4, type=jar}
/spark-gremlin
Dependency {groupId=org.xerial.snappy, artifactId=snappy-java,
version=1.1.8.2, type=jar}
/hadoop-gremlin
---------
Dependency com.fasterxml.jackson.core:jackson-databind:jar has inconsistent
versions between modules.
Dependency {groupId=com.fasterxml.jackson.core,
artifactId=jackson-databind, version=2.15.2, type=jar}
/gremlin-shaded
Dependency {groupId=com.fasterxml.jackson.core,
artifactId=jackson-databind, version=2.13.5, type=jar}
/spark-gremlin
/hadoop-gremlin
---------
```
# 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.
# 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.
Summary: Dependency inconsistency between modules. (was: Inconsistent )
> Dependency inconsistency between modules.
> -----------------------------------------
>
> Key: TINKERPOP-3060
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3060
> Project: TinkerPop
> Issue Type: Improvement
> Reporter: Wei Zhao
> Priority: Minor
> 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.
> ```
> Dependency com.google.guava:guava:jar has inconsistent versions between
> modules.
> Dependency {groupId=com.google.guava, artifactId=guava, version=31.1-jre,
> type=jar}
> /gremlin-annotations
> Dependency {groupId=com.google.guava, artifactId=guava, version=27.0-jre,
> type=jar}
> /spark-gremlin
> /hadoop-gremlin
> ---------
> Dependency org.xerial.snappy:snappy-java:jar has inconsistent versions
> between modules.
> Dependency {groupId=org.xerial.snappy, artifactId=snappy-java,
> version=1.1.8.4, type=jar}
> /spark-gremlin
> Dependency {groupId=org.xerial.snappy, artifactId=snappy-java,
> version=1.1.8.2, type=jar}
> /hadoop-gremlin
> ---------
> Dependency com.fasterxml.jackson.core:jackson-databind:jar has inconsistent
> versions between modules.
> Dependency {groupId=com.fasterxml.jackson.core,
> artifactId=jackson-databind, version=2.15.2, type=jar}
> /gremlin-shaded
> Dependency {groupId=com.fasterxml.jackson.core,
> artifactId=jackson-databind, version=2.13.5, type=jar}
> /spark-gremlin
> /hadoop-gremlin
> ---------
> ```
> 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)
