Unexpected Maven version selection causing runtime linkage errors
In a multi‑module Maven project, a dependency is declared with version 2.5.0 in the POM (or dependencyManagement) but at runtime a ClassNotFoundException indicates that an older version 2.3.1 is being loaded. The build shows no explicit version conflict warnings, and the effective POM still lists 2.5.0 for the artifact, yet the resolved JAR on the classpath
maven