This seems to have been caused by changes for issue LDAP-311.
When starting up an application that uses Spring LDAP with XML config, the exception is thrown on init:
org.springframework.beans.FatalBeanException: Invalid NamespaceHandler class [org.springframework.ldap.config.LdapNamespaceHandler] for namespace [http://www.springframework.org/schema/ldap]: problem with handler class file or dependent class; nested exception is java.lang.NoClassDefFoundError: org/springframework/data/repository/config/RepositoryConfigurationExtension
Adding spring-data-commons dependency resolves this issue.
Migrated from LDAP-335
This seems to have been caused by changes for issue LDAP-311.
When starting up an application that uses Spring LDAP with XML config, the exception is thrown on init:
org.springframework.beans.FatalBeanException: Invalid NamespaceHandler class [org.springframework.ldap.config.LdapNamespaceHandler] for namespace [http://www.springframework.org/schema/ldap]: problem with handler class file or dependent class; nested exception is java.lang.NoClassDefFoundError: org/springframework/data/repository/config/RepositoryConfigurationExtension
Adding spring-data-commons dependency resolves this issue.