Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

separate framework code and lib dependencies for seata-server fatjar deployments #4669

Closed
1 task
slievrly opened this issue Jun 8, 2022 · 1 comment · Fixed by #4711
Closed
1 task
Assignees
Labels
task: help-wanted Extra attention is needed

Comments

@slievrly
Copy link
Member

slievrly commented Jun 8, 2022

  • I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description

separate framework code and lib dependencies for seata-server fatjar deployments

The fatjar deployment package is too large. In use, the efficiency of development, operation and maintenance is affected because several lines of code are modified but hundreds MB of fatjar deployment needs to be uploaded. In addition, it is not conducive to the expansion and replacement of jar package dependency.
image


分离 seata-server 部署时的框架和lib依赖

fatjar 部署包的体积过大。在使用中因为修改几行代码但是却需要上传上百M 的fatjar部署,影响开发运维的效率。另外,不利于jar包依赖的扩展和替换。

Ⅱ. Describe what happened

If there is an exception, please attach the exception trace:

Just paste your stack trace here!

Ⅲ. Describe what you expected to happen

Ⅳ. How to reproduce it (as minimally and precisely as possible)

  1. xxx
  2. xxx
  3. xxx

Ⅴ. Anything else we need to know?

Ⅵ. Environment:

  • JDK version :
  • Seata version: 1.5.1
  • OS :
  • Others:
@slievrly slievrly added the task: help-wanted Extra attention is needed label Jun 8, 2022
@slievrly slievrly self-assigned this Jun 16, 2022
@slievrly
Copy link
Member Author

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task: help-wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant