[BUG] Use jar-with-dependencies to package frontend artifacts in GIE · alibaba/GraphScope#2938

(1 comment) (0 reactions) (0 assignees)HTML (2,401 stars) (301 forks)batch import

component:dev-infracomponent:giegood first issuejavapriority:high

説明

Describe the bug

It is quite superised that we didn't use jar-with-dependency to package the release artifacts for java. Recent changes about neo4j introduced some new jar dependency, double the size of the wheel package (https://pypi.org/project/graphscope/0.23.0a20230625/#files), makes graphscope hard to install with python ....

Expected Outcome

The ultimate goal is to reduce the size of wheels, which in this issue, is the artifacts of interactive engine. You could observe the size of artifacts of gie by make interactive and find graphscope.tar.gz within interactive_engine/assembly/target

Additional context Add any other context about the problem here.

コントリビューターガイド

技術スタック: java
領域: build system
Issue 種別: bug
難度: 3
推定時間: 1-3 hours
活動状況: stale
明確さ: clear
前提条件: MavenJava packaging
初心者向け度: 65
調査方針: Investigate the current Maven packaging configuration in the interactive engine assembly module (likely in interactive engine/assembly/pom.xml). Modify the pom.xml to use the jar with dependencies classifier to bundle dependencies into a single jar. Then run 'make interactive' to verify the build and check the size of graphscope.tar.gz in interactive engine/assembly/target. Ensure that the wheel package size is reduced as expected.