EnvGap
[BUG] Package Version Conflict Error when Introducing Neo4j Maven Dependency in Groot Server Module
envgap__alibaba__GraphScope-2890
01 / FAILURE SIGNATURE
As reported upstream
When attempting to introduce the Neo4j Maven dependency in the Groot Server Module, a package version conflict error occurs. The conflict arises from the differing Scala versions required by Kafka and Neo4j. Kafka, which is originally a dependency of the Groot Server Module, relies on Scala 2.13, while Neo4j requires Scala 2.12. This conflicting dependency causes runtime errors.
Not a benchmark task.
- In a clean container the reported failure did not reproduce, or the known fix did not make the project run.
02 / ENVIRONMENT RECIPE
- Base commit
c2d15dd8149f3b4529de177099e1a4b2626f8295- Manifest
interactive_engine/pom.xml- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
alibaba/GraphScope #2890 · read the original issue
**Describe the bug** When attempting to introduce the Neo4j Maven dependency in the Groot Server Module, a package version conflict error occurs. The conflict arises from the differing Scala versions required by Kafka and Neo4j. Kafka, which is originally a dependency of the Groot Server Module, relies on Scala 2.13, while Neo4j requires Scala 2.12. This conflicting dependency causes runtime errors. **To Reproduce** Steps to reproduce the behavior: 1. Add the Neo4j Maven dependency to the Groot Server Module. 2. Attempt to build the project or start the Groot Server. 3. Observe the package version conflict error related to Scala. **Expected behavior** The Neo4j Maven dependency should be successfully integrated into the Groot Server Module without causing any package version conflict errors. **Environment (please complete the following information):** - GraphScope version: [main] - OS: [Linux]
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]