directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <directory-...@incubator.apache.org>
Subject [jira] Commented: (DIRNAMING-7) Package artifacts into a more modular set of jars
Date Sun, 26 Dec 2004 02:47:04 GMT
     [ http://nagoya.apache.org/jira/browse/DIRNAMING-7?page=comments#action_57052 ]
     
Phil Steitz commented on DIRNAMING-7:
-------------------------------------

Thanks. One jar per subproject is certainly simpler.  We will just need to make sure that
the site gets generated correctly (esp. javadoc) and we have clear build instructions. 

I keep wanting to do "multiproject:clean test" to rebuild and run all of the tests, for example;
but this does not seem to exist.  I have to do maven jar:install from core and then clean:test
from factory. This will get more complicated as we split things up further.  Maybe I am missing
something?  Do we need custom goals to do this in maven.xml?

> Package artifacts into a more modular set of jars
> -------------------------------------------------
>
>          Key: DIRNAMING-7
>          URL: http://nagoya.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://nagoya.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


Mime
View raw message