You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <di...@incubator.apache.org> on 2004/11/01 05:28:32 UTC
[jira] Created: (DIREVE-75) cleanup the eve directory structure
cleanup the eve directory structure
-----------------------------------
Key: DIREVE-75
URL: http://issues.apache.org/jira/browse/DIREVE-75
Project: Directory Eve
Type: Wish
Reporter: Alex Karasulu
Assigned to: Alex Karasulu
Nothing right now is as it seems and its all too cryptic for an interested party to find what they want. What's the deal with this core directory. We need to have the following setup for Eve:
eve/trunk...
-->shared for common shared resource, interfaces and modules to break build dependency cycles
-->jndi-provider for the Eve JNDI (LDAP namespace) Provider which effectively is synonymous with the backend subsystem
-->ldap-protocol the SEDA protocol provider for the LDAP protocol
-->tools various tools for developing Eve or using Eve
We can then use a nice multiproject build to get all this crud building like a champion. Right now we got a nasty cycle between the plugin and the jndi-provider which is now under eve/trunk/backend/core.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (DIREVE-75) cleanup the eve directory structure
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-75?page=history ]
Alex Karasulu closed DIREVE-75:
-------------------------------
Resolution: Fixed
Done en toto!!!!
> cleanup the eve directory structure
> -----------------------------------
>
> Key: DIREVE-75
> URL: http://issues.apache.org/jira/browse/DIREVE-75
> Project: Directory Eve
> Type: Wish
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
>
> Nothing right now is as it seems and its all too cryptic for an interested party to find what they want. What's the deal with this core directory. We need to have the following setup for Eve:
> eve/trunk...
> -->shared for common shared resource, interfaces and modules to break build dependency cycles
> -->jndi-provider for the Eve JNDI (LDAP namespace) Provider which effectively is synonymous with the backend subsystem
> -->ldap-protocol the SEDA protocol provider for the LDAP protocol
> -->tools various tools for developing Eve or using Eve
> We can then use a nice multiproject build to get all this crud building like a champion. Right now we got a nasty cycle between the plugin and the jndi-provider which is now under eve/trunk/backend/core.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira