One way to solve this since the Commons idea is a good one, and
different in deliverables than 'regular' jakarta projects, we could look
at changing whatever Avalon's charter really is to include the
productized component project there (Library).
Of course, this would be a decision by the Avalon folk to change their
model of dealing with components. I only bring this up because I get the
sense that the Avalon folk are interested.
David Weinrich wrote:
> Jakarta
> |
> | -> Tomtcat
> | -> Commons
> | |
> | |->Agora
> | | |-> A collection of projects in the process of creating
> | | components, with people collaborating from different
> | | jakarta projects.
> | |
> | |->Catalog
> | | |-> Searchable links to what is available where.
> |
| -> Avalon
| |
| |-> server framework thingy
| |
> | |->Library
> | | |
> | | |-> DBConnectionPool
> | | |-> XMLCOnfig
> | | |-> A set of reusable components that have reached a stable
> | point in their lifecycle and meet standards for support
> | infrastructure and documentation.
> |
> | -> Turbine
>
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
