-
Notifications
You must be signed in to change notification settings - Fork 200
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
[Good first issue] Add gradle enforcer plugin to avoid potential dependency conflict issues #1085
Comments
assigned to me. I have configured the enforcer plugin with the DependencyConvergence rule and encountered several version conflict issues, such as: Dependencies conflict from |
Cool, asigned! @Gezi-lzq |
is it still available? i would like to work on it pls let me know.. |
Hi, it's available, but it's a bit complex since tons of conflict dependencies should be resolved. You can take over this issue or find other good first issues. And thanks for your interest in AutoMQ. |
Background
AutoMQ may be failed in the runtime environment occasionally, due to dependency conflict issues.
What's our expectation for the issue
Add gradle enforcer plugin to avoid such risks.
How to started
Add this plugin to our build system: https://kordamp.org/enforcer-gradle-plugin/
Reference
Maven also support enforcer plugin, just for reference: https://maven.apache.org/enforcer/maven-enforcer-plugin/index.html
The text was updated successfully, but these errors were encountered: