Closed adispennette closed 9 years ago
I believe this is another symptom of spring-io/platform#98. Unfortunately, breaking API changes were made between ApacheDS 1.5.5 and 1.5.7. The problem's fixed in Spring IO Platform 1.0.4 snapshots by dropping back to 1.5.5. You can either use the snapshots, or continue to use 1.0.3 but override apacheds.version
:
<parent>
<groupId>io.spring.platform</groupId>
<artifactId>platform-bom</artifactId>
<version>1.0.3.RELEASE</version>
</parent>
<properties>
<start-class>hello.Application</start-class>
<apacheds.version>1.5.5</apacheds.version>
</properties>
Thank you for the prompt reply
I am using
because of some of the additional dependencies it manages. but when using this in conjuction with this example there are many points of failure. The apacheds artifact for version 0.9.15 does not have the ServerEntry class and when updating the version to 0.9.19 the LdapNameNotFoundException is not found because it is in version 0.9.18. So I thought adding apacheds-all would fix this but that was not the case. this is because the managed version, and I assume all versions, of the apacheds-all has the 1.5 version of org.slf4j packaged in the jar which causes a version conflict when doing the slf4j binding.
I am of the opinion that there are 2 defect here, one with the spring-io pom and one with the apacheds-all artifact. if you do not agree please let me know and close this ticket.
Thanks,