AutoMQ/automq

[Good first issue] Add gradle enforcer plugin to avoid potential dependency conflict issues

Opened this issue · 4 comments

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

assigned to me.

I have configured the enforcer plugin with the DependencyConvergence rule and encountered several version conflict issues, such as:

Dependencies conflict from io.swagger.core.v3:swagger-jaxrs2, including jackson and commonLang.
Dependencies conflict related to netty introduced by software.amazon.awssdk:netty-nio-client:2.20.127.
Dependencies conflict from com.google.guava:guava:32.0.1-jre, including checker-qual and errorprone.

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.