Leo Simons wrote:
> as per the front page:
>
> "Excalibur is a collection of often-needed reusable components. It
> includes tools for threading, pooling, datasources, proxies and more."
They are moving to Commons.
> as it has been talked about recently:
>
> "Excalibur is a collection of containers and utilities for the building
> of containers.
>
> (note: Excalibur used to contain many reusable components. These have
> been moved to jakarta-commons, or are in the process of being moved.)"
+1
> and with a sandbox thrown in:
>
> "Excalibur is a collection of containers and utilities for the building
> of containers.
>
> (note: Excalibur used to contain many reusable components. These have
> been moved to jakarta-commons, or are in the process of being moved.)
>
> It also contains our 'sandbox', where we prototype new avalon bits. We
> keep this separate from the jakarta-commons-sandbox since we deal with
> very avalon-specific material here."
Hmmm... I would state more clearly that code that is not tied to Avalon
framework should not be created here anyway, and *will* be created in
commons-sandbox, as I'm doing with the commons-pattern package.
> which one for the future? (this is not a vote, I'd just like to hear
> your thoughts)
Cool :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
