Manage dependencies at the top level using `` to ensure version consistency across modules and prevent conflicts. Define version properties in one place and reference them throughout the project: ```xml 2.15.0 1.33 com.fasterxml.jackson.core jackson-databind ${jackson.version} io.netty netty-all ${netty.version} ``` In module pom files, reference dependencies without version numbers: ```xml com.fasterxml.jackson.core jackson-databind ``` Avoid: - Release candidate (RC) or SNAPSHOT versions in production code - Downgrading library versions - Using generic version references like `${project.version}` or `${project.parent.version}` - Different versions of the same underlying libraries (e.g., JavaCPP) For related but distinct libraries (like Netty 3.x vs 4.x), create separate version properties (e.g., `netty3.version` and `netty.version`) to clearly distinguish them.