[ http://issues.apache.org/jira/browse/DIREVE-229?page=comments#action_12319730 ]
Alex Karasulu commented on DIREVE-229: -------------------------------------- Let me note first that there is no maven project cyclicity. ApacheDS is a top level project within our repo and one of its subprojects the 'main' subproject depends on the ldap protocol provider. It has to. However the ldap protocol provider has a dependency on the 'core' subproject of ApacheDS so there really is no cyclicity here in terms of Maven otherwise we'd have much more serious isses with the build. I think this issue my be unnecessary. WDYT with this additional knowledge? Perhaps we need to create a separate group id and project for the main stuff. Perhaps the main stuff goes away when we do OSGi. > Cycle in compilation > -------------------- > > Key: DIREVE-229 > URL: http://issues.apache.org/jira/browse/DIREVE-229 > Project: Directory Server > Type: Improvement > Components: server main > Reporter: Emmanuel Lecharny > Priority: Minor > > There is a cycle in compilation process : > - apacheds depends on protocol-provider-ldap > - protocol-provider-ldap depends on apacheds > The class BindHandler in protocol-provider-ldap import those two classes : > import org.apache.ldap.server.configuration.Configuration; > import org.apache.ldap.server.configuration.StartupConfiguration; > which are declared in apacheds/core. > It can't be fix easily, as those classes are used to get information about > configuration to avoid non authorized Bind. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
