ConflictingBeanDefinitionException after Intellij refactoring

Question

I encounter a ConflictingBeanDefiitionException saying that org.company.app.core.controller.web.EquipmentController conflicts with org.company.app.core.controller.EquipmentController. The only problem is the lack of org.company.app.core.controller.EquipmentController. It used to be, I moved it to the org.company.app.core.controller.web package.

I do not understand why this is happening. Is this a strange Intellij thing or what?

Caused by: org.springframework.context.annotation.ConflictingBeanDefinitionException: Annotation-specified bean name 'equipmentController' for bean class [org.company.app.core.controller.web.EquipmentController] conflicts with existing, non-compatible bean definition of same name and class [org.company.app.core.controller.EquipmentController]
    at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.checkCandidate(ClassPathBeanDefinitionScanner.java:320)
    at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:259)
    at org.springframework.context.annotation.ComponentScanAnnotationParser.parse(ComponentScanAnnotationParser.java:140)
    at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:262)
    at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:226)
    at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:480)
    ... 59 more

Answer 1

mvn clean package

Worked for me. It tries to clean files and directories created by Maven during its old build.