If a project depends on rice-kim-api, an institutional kim impl for example, an older dependency of commons-collections (3.1) will be resolved by maven. This causes compilation errors. The kim api code uses commons-collections classes, but it doesn't declare a dependency (it gets the older version from db-ojb). While the proper version is declared in the dependencyManagement of the Rice parent, this doesn't seem to affect external projects. Adding commons-collections as an explicit dependency seems warranted and will resolve the problem for external projects.