directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lécharny <elecha...@gmail.com>
Subject Re: Unit tests for ldap api classes
Date Sat, 03 May 2014 23:33:53 GMT
Le 5/3/14 11:50 PM, Stefan Seelmann a écrit :
> On 05/03/2014 11:30 PM, Emmanuel Lécharny wrote:
>> Le 5/3/14 10:20 PM, Stefan Seelmann a écrit :
>>> On 05/03/2014 10:08 PM, Emmanuel Lécharny wrote:
>>>> Le 5/3/14 10:03 PM, Stefan Seelmann a écrit :
>>>>> Hi Emmanuel,
>>>>>
>>>>> yes, I think your proposal makes sense.
>>>>>
>>>>> However I still see some circular dependencies that needs to be solved.
>>>> Like ?
>>> ldap-client integration tests (if also moved to the client project) need
>>> apacheds.
>>>
>>> apacheds integration tests need ldap-client
>> api-ldap-client-api, which is from shared.
>>
>> I don't think we have cyclic dependenxy here...
> If
> - shared/api-ldap-client-api is moved to clients/trunk/ldap and
> - apacheds/ldap-client-test is moved to clients/trunk/ldap too
>
> then we have, because apacheds modules depend on api-ldap-client-api and
> ldap-client-test depends on apacheds modules. Ok, only on project level,
> not on module level.

Ok, but why should we move api-ldap-client-api to clients/trunk/ldap ?

What I had in mind was just to move aâcheds/ldap-client-test to
client/trunk/ldap. In this case, we should not have any cyclic dependency.


It's a bit late here, so I may miss something...


-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com 


Mime
View raw message