Skip to content

fix: resolve dependency conflicts using resolutionStrategy (issue #1085)#3071

Closed
OmpalYadav wants to merge 2 commits intoAutoMQ:mainfrom
OmpalYadav:fix/dependency-conflict-1085
Closed

fix: resolve dependency conflicts using resolutionStrategy (issue #1085)#3071
OmpalYadav wants to merge 2 commits intoAutoMQ:mainfrom
OmpalYadav:fix/dependency-conflict-1085

Conversation

@OmpalYadav
Copy link
Copy Markdown

Resolves #1085

Background

The build was failing due to multiple dependency version conflicts. The previously suggested enforcer plugin was causing compatibility issues with Gradle 8.8.

Changes

  • Removed the incompatible org.kordamp.gradle.enforcer plugin.
  • Enabled Gradle's native failOnVersionConflict() strategy in build.gradle.
  • Resolved version conflicts for Scala, Netty, Jackson, Jetty, BouncyCastle and other libraries by forcing consistent versions via resolutionStrategy.

Verification

  • Ran ./gradlew build -x test locally.
  • Build passed successfully without dependency conflict errors.

@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Nov 28, 2025

CLA assistant check
All committers have signed the CLA.

@OmpalYadav OmpalYadav changed the title Fix: Resolve dependency conflicts using resolutionStrategy (Issue #1085) fix: resolve dependency conflicts using resolutionStrategy (issue #1085) Nov 28, 2025
@OmpalYadav
Copy link
Copy Markdown
Author

@1sonofqiu @Gezi-lzq

Hi there! 👋

Good news: The Unit Tests passed, which confirms that the dependency conflicts are resolved correctly. ✅

However, the Checkstyle job failed.
Looking at the logs, it seems that forcing com.google.protobuf:protobuf-java:3.25.5 caused the generated files (specifically PersonProto.java) to have a different indentation style than what the current Checkstyle configuration expects.

Since this is auto-generated code, I didn't want to manually edit it.
Question: Should I try to downgrade Protobuf to an older compatible version, or is there a standard way to regenerate/update the style for this project?

Awaiting your advice. Thanks!

@Gezi-lzq
Copy link
Copy Markdown
Contributor

Thank you for your contribution, we will review this soon.

@github-actions
Copy link
Copy Markdown

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.

@github-actions github-actions Bot added the Stale label Mar 12, 2026
@github-actions github-actions Bot closed this Apr 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

3 participants