[ http://issues.apache.org/jira/browse/DIRNAMING-7?page=history ]
Phil Steitz closed DIRNAMING-7:
-------------------------------
Resolution: Fixed
Repackaging has been completed
> Package artifacts into a more modular set of jars
> -------------------------------------------------
>
> Key: DIRNAMING-7
> URL: http://issues.apache.org/jira/browse/DIRNAMING-7
> Project: Directory naming
> Type: Improvement
> Reporter: Phil Steitz
> Assignee: Phil Steitz
>
> The current naming-factory and naming-core division is not the best setup. As discussed
on directory-dev, we should change the deployed artifacts to follow the tomcat-5 division:
>
> naming-core (tc calls this naming-common)
> Everything in o.a.naming plus o.a.naming.factory.ResourceLinkFactory and
> o.a.naming.factory.ResourceLinkFactory.Constants
> Includes basic naming service and context impl
> Depends on JMX for NamingService
> naming-factory
> Object factories
> Everything in o.a.naming.factory
> Depends on core and the mail API spec to compile; if used, mail session
> and database connection pool builtins require javamail and commons-dbcp,
> resp.
> naming-java
> Only JavaURLContextFactory
> Depends on core
>
> naming-resources
> JNDI access to file / stream resources
> o.a.c.naming.resources
> Depends on core and commons collections
>
> naming-config
> Contents of o.a.c.naming.config
> Depends on core, and commons beanutils, digester, lang, and logging
>
--
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
|