Peter Donald wrote:
> At 09:18 1/3/01 -0800, [EMAIL PROTECTED] wrote:
> >Arguing that this should be part of avalon because it overlaps with
> >it's goal is wrong - the library will overlap with almost all
> >jakarta projects. It overlaps with jakarta-tools ( which also overlaps
> >with avalon ), it overlaps with alexandria. All jakarta
> >projects are creating some forms of server-side compoents
> >( including tomcat ).
>
> But Avalon was intended to be a shared repository of server-side components
> - it has no other purpose ;) All the other projects create server-side
> components as a side effect of developing another product. Avalons product
> is the components.
>
Peter, when you say "components" here, I need a clarification. Do you mean "a
chunk of reusable code" or "a chunk of reusable code that implement's Avalon's
notion of a Component interface"? These are two entirely different things. If
it's the former, I'd still prefer agora/commons/whatever to be separate -- if it's
the latter, then that's just as presumptive as me saying it should live in Struts,
or Jon saying it should live in Turbine (neither of which is happening).
The shareable stuff I'm interested in is smaller than a framework --- any
framework.
Craig McClanahan
