fix: resolve dependency conflicts using resolutionStrategy (issue #1085)#3071
fix: resolve dependency conflicts using resolutionStrategy (issue #1085)#3071OmpalYadav wants to merge 2 commits intoAutoMQ:mainfrom
Conversation
|
Hi there! 👋 Good news: The Unit Tests passed, which confirms that the dependency conflicts are resolved correctly. ✅ However, the Checkstyle job failed. Since this is auto-generated code, I didn't want to manually edit it. Awaiting your advice. Thanks! |
|
Thank you for your contribution, we will review this soon. |
|
This PR is being marked as stale since it has not had any activity in 90 days. If you would like to keep this PR alive, please ask a committer for review. If the PR has merge conflicts, please update it with the latest from trunk (or appropriate release branch) If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed. |
Resolves #1085
Background
The build was failing due to multiple dependency version conflicts. The previously suggested
enforcerplugin was causing compatibility issues with Gradle 8.8.Changes
org.kordamp.gradle.enforcerplugin.failOnVersionConflict()strategy inbuild.gradle.resolutionStrategy.Verification
./gradlew build -x testlocally.