tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Duncan Davidson" <james.david...@eng.sun.com>
Subject Re: [Vote] Package structure, code sharing and project proposal
Date Thu, 04 Nov 1999 01:44:09 GMT
> 2) each independent project (the PMC boards or general consensus will
> decide if this applies) will follow the package
>
>     org.apache.<project_name>

+1 -- note this is what we do in Jakarta land already (org.apache.tomcat,
etc).

>  c) "share"  -> org.apache.share

+1

> a) general consensus and strong contract: all projects must agree on the
> general consensus or the share classes will provide more harm than good.
>
> b) creation of a project to control the shared code with own CVS module.
>
> c) integration with the other projects with stronger CVS and
> distribution link (separate jar files to avoid code duplication in
> classpath).
>
> d) creation of the board to control the project and a public mail list
> for discussion.
>
> e) relation to the Java API and other shared libraries: should this
> project be targetted to create a server-side utility API for external
> projects as well? Sort of CPAN for general utility classes?

I know that Brian probably wants to pause on considering this until we get a
few other fires down (and I concur! :) -- but this is an issue that we have
to deal with at some point in the future.




Mime
View raw message