When using a @MapperScan I receive the warning:
15:32:22.435 [MainThread] WARN o.m.s.mapper.ClassPathMapperScanner - Skipping MapperFactoryBean with name 'configurationMapper' and 'com.imc.naiad.subscriber.dao.ConfigurationMapper' mapperInterface. Bean already defined with the same name!
15:32:22.444 [MainThread] WARN o.m.s.mapper.ClassPathMapperScanner - No MyBatis mapper was found in '[com.imc.naiad.subscriber.dao]' package. Please check your configuration.
I tracked this down to a Spring issue. When an annotation uses an @Import (as @MapperScan does) Spring will scan the @Import class twice. I've filed a Spring bug here:
https://jira.springsource.org/browse/SPR-10918. In the interim we could remove the @Import annotation from @MapperScan and let the client add the import themselves. This is how I've worked around the error message locally.