-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
使用了外部依赖的插件在开发模式下出现 NoClassDefFoundError 问题 #3107
Labels
kind/improvement
Categorizes issue or PR as related to a improvement.
Milestone
Comments
@guqing: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/kind improvement |
f2c-ci-robot
bot
added
the
kind/improvement
Categorizes issue or PR as related to a improvement.
label
Jan 6, 2023
f2c-ci-robot bot
pushed a commit
that referenced
this issue
Jan 9, 2023
…3108) #### What type of PR is this? /kind improvement /area core /milestone 2.2.x #### What this PR does / why we need it: 修复引入外部依赖的插件以开发模式启动时会出现 NoClassDefFoundError 的问题 see #3107 for more detail. #### Which issue(s) this PR fixes: Fixes #3107 #### Special notes for your reviewer: how to test it? 以插件 development 模式启动以下两个插件观察是否正常启动: - https://github.com/halo-sigs/plugin-s3 - https://github.com/halo-sigs/plugin-alioss 期望没有 `Caused by: java. lang. NoClassDefFoundEenon` 错误,且插件正确启动。 /cc @halo-dev/sig-halo #### Does this PR introduce a user-facing change? ```release-note 修复引入外部依赖的插件以开发模式启动时会出现 NoClassDefFoundError 的问题 ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is version of Halo has the issue?
latest
What database are you using?
H2
What is your deployment method?
Docker
Your site address.
No response
What happened?
此问题仅开发模式存在,导致无法使用开发模式,jar 包可以正常使用。
Relevant log output
异常示例:
Additional information
/kind improvement
/milestone 2.2.x
/assign
The text was updated successfully, but these errors were encountered: