Hello Stefan, sorry for personal replies (I just hit 'Reply All')
Thanks a lot for the link to apacheds-test-framework It works as expected and contains all necessary classes (including `CreateLdapServerRule`) So I was able to create my first tests :) Our application uses `api-all` to communicate with LDAP server This is why I have "schema conflict" I'll try to contribute to 7-embedding-apacheds.mdtext <https://svn.apache.org/repos/asf/directory/site/trunk/content/apacheds/advanced-ug/7-embedding-apacheds.mdtext> later today/tomorrow (was unable to find git repo for site) so will send complete file Thanks a lot for the help! On Tue, 30 Oct 2018 at 02:12, Stefan Seelmann <[email protected]> wrote: > On 10/29/18 1:29 PM, Maxim Solodovnik wrote: > > Thanks for the answer Stefan, > > > > I'm trying to write my first test > > > > Here are some findings and questions: > > > > 1) It seems `org.apache.directory.api:api-all` and > > `org.apache.directory.api:api-ldap-schema-data` have conflicting ldif > > bundled, is it safe to exclude api-ldap-schema-data from > > `org.apache.directory.server:apacheds-server-integ` ? > > As written in the other mail, please don't use server-integ or > core-integ as dependency, but apacheds-test-framework. > > I guess the duplication is because api-all is a fat jar which contains > all other api modules and dependences (using maven-shade-plugin). But > it's strange that you have api-all, I don't see it as dependency in > server-integ (using mvn dependency:tree)... > -- WBR Maxim aka solomax
