@ssmusoke , im my case i was adding a new conditional resource2.2 in the reporting module see work done ,
it was heavily due to conflicting bean definitions , that is between xml definitions in pre-2.2 core version and Annotation definition in 2.2 core version.
I solved it by deeply and carefully looking at the dependency definitons in the Parent Pom and the Child POM of sub resource 2.2.
The idea is ensure the Child POM file for sub resource 2.2 entirely depends on Core 2.2 API only.
theres a tendence where it will both pull dependencis from core 2.2 and core pre-2.2 version ,and that will cause Conflicts , because in core 2.2. some spring bean definitions were switched to annotation rather than XML.
You can actually add exclusions in the Child POM to exclude any component that is still inherited by child POM from the Parent pom