You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Phil Steitz (JIRA)" <di...@incubator.apache.org> on 2004/12/25 22:53:03 UTC

[jira] Created: (DIRNAMING-7) Package artifacts into a more modular set of jars

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
 Assigned to: 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


[jira] Commented: (DIRNAMING-7) Package artifacts into a more modular set of jars

Posted by "Phil Steitz (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIRNAMING-7?page=comments#action_57081 ]
     
Phil Steitz commented on DIRNAMING-7:
-------------------------------------

Just committed reorg to support structure above with one addition:

directory-managment, per Hen's suggestion pulls out the jmx stuff.

> 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


[jira] Commented: (DIRNAMING-7) Package artifacts into a more modular set of jars

Posted by "Henri Yandell (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIRNAMING-7?page=comments#action_57046 ]
     
Henri Yandell commented on DIRNAMING-7:
---------------------------------------

config in its own module now.

> 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


RE: [jira] Commented: (DIRNAMING-7) Package artifacts into a more modular set of jars

Posted by Stephen McConnell <mc...@apache.org>.

> -----Original Message-----
> From: Phil Steitz (JIRA) [mailto:directory-dev@incubator.apache.org]
> 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?

Maven is very much focused on one artifact per project.  Best to
rearrange you structure such that you have a separate project per jar.

Cheers, Steve.




[jira] Commented: (DIRNAMING-7) Package artifacts into a more modular set of jars

Posted by "Phil Steitz (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIRNAMING-7?page=comments#action_57048 ]
     
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: 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


[jira] Commented: (DIRNAMING-7) Package artifacts into a more modular set of jars

Posted by "Brett Porter (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIRNAMING-7?page=comments#action_57050 ]
     
Brett Porter commented on DIRNAMING-7:
--------------------------------------

it's definitely going to be clearer with Maven if you separate it into separate projects to keep it as one jar per project.

the way I'd think about it is that if there is a clear reason to separate the binaries (as there is), then it makes sense to do likewise with the source.

> 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


[jira] Commented: (DIRNAMING-7) Package artifacts into a more modular set of jars

Posted by "Henri Yandell (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIRNAMING-7?page=comments#action_57047 ]
     
Henri Yandell commented on DIRNAMING-7:
---------------------------------------

Tomcat's separation choice is interesting. Notably, separating out the java class seems pretty unnecessary, and separating out the JMX class seems desirable.

We could move the MBean and its Service class into its own one; naming-management. We could keep the java class in the core package.

I'm still unsure as to why we have some of the Ref classes in core that only factory needs. Tempting to think they should be moved over.

> 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


[jira] Commented: (DIRNAMING-7) Package artifacts into a more modular set of jars

Posted by "Phil Steitz (JIRA)" <di...@incubator.apache.org>.
     [ 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


[jira] Closed: (DIRNAMING-7) Package artifacts into a more modular set of jars

Posted by "Phil Steitz (JIRA)" <di...@incubator.apache.org>.
     [ 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


[jira] Commented: (DIRNAMING-7) Package artifacts into a more modular set of jars

Posted by "Brett Porter (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIRNAMING-7?page=comments#action_57053 ]
     
Brett Porter commented on DIRNAMING-7:
--------------------------------------

"multiproject:clean multiproject:install" will clean, test, and install all.

multiproject:site will do the site. Unfrotunately, aggregation of javadoc is not currently possible, but something I've spoken to Alex about and is wanted in a variety of projects within directory, and something also wanted elsewhere.



> 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