Resolving the java.lang.NoSuchMethodError in Hibernate Validator: A Guide for Quarkus Users

---

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---

Understanding the Problem

[[See Video to Reveal this Text or Code Snippet]]

After introducing this dependency, you encountered the following error during the build process:

[[See Video to Reveal this Text or Code Snippet]]

Why This Happens

The error indicates that there’s a missing method that Hibernate Validator expects to find. This typically occurs due to transitive dependencies that might not be compatible with the version you are currently using. This means that while your direct dependencies are updated, some indirect or transitive dependencies might still reference previous versions, leading to conflicts.

Solution: Exclude the Transitive Dependency

To resolve the NoSuchMethodError, here’s a succinct solution you can implement:

Identify the Transitive Dependency: Determine which transitive dependency of Hibernate Validator is causing the issue.

Here’s how you can exclude it in Gradle:

[[See Video to Reveal this Text or Code Snippet]]

Why Exclude the Transitive Dependency?

Prevents Conflicts: Excluding outdated or incompatible versions of a library helps ensure that your application uses only compatible versions, thus reducing the chances of encountering NoSuchMethodError.

Ensures Clarity: It makes the dependencies clearer and helps in understanding which versions of libraries are being used.

Verifying Your Setup

After making these changes, perform a clean build of your application:

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

For developers working with Quarkus and Hibernate Validator, staying updated on dependency compatibility is essential for smooth upgrades. If you follow the steps outlined in this post, you'll be well on your way to maintaining a stable and efficient development environment.