conflicts with existing, non-compatible bean definition of same name and class after proguard obfuscation

obfuscation, proguard, spring

Solution

I'm not sure if this is what you want, but you can specify bean name in @Component (and stereotypes @Repository, @Service and @Controller) value:

@Component("myBeanName")
public class MyBean {

}

Problem

after Proguard obfuscation i get the following error : Unexpected exception parsing XML document from ServletContext resource [/WEB-INF/applicationContext.xml]; nested exception is java.lang.IllegalStateException: Annotation-specified bean name 'a' for bean class [com.company.project.b.a.a.a] conflicts with existing, non-compatible bean definition of same name and class [com.company.project.a.a] i'm using annotation based spring configuration , how can i avoid having two classes with the same name using Proguard because Spring doesn't allow two beans to have the same name.

Original source