Skip to content

Conversation

@OmpalYadav
Copy link

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

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
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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

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

2 participants