directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <>
Subject [jira] Commented: (DIRNAMING-7) Package artifacts into a more modular set of jars
Date Sun, 26 Dec 2004 01:09:04 GMT
     [ ]
Phil Steitz commented on DIRNAMING-7:

I think that tomcat may separate java to avoid conflicts when tomcat is embedded inside another
container (think I saw a comment to that effect somewhere).  It is probably best that we follow
tc here.

I suspect that having o.a.naming.factory.ResourceLinkFactory and 
o.a.naming.factory.Constants in core is so that core + resources can be used to setup file
and war dircontexts, without dragging in the rest of the factories. 

I would be OK with splitting out the JMX bits in core.

One naive question: is it a forgone conclusion that the right way to do this is to chop up
the source tree into mutually exclusive subprojects?   Alternatively, couldn't we define custom
jar targets a la ant using includes / excludes based on a single common source tree? What
is the right way to do this using maven? 

> Package artifacts into a more modular set of jars
> -------------------------------------------------
>          Key: DIRNAMING-7
>          URL:
>      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:
If you want more information on JIRA, or have a bug to report see:

View raw message