Peter Donald wrote:
>
> At 08:04 26/2/01 -0800, [EMAIL PROTECTED] wrote:
> >The only (detail) I'm still woried about in the library project is the
> >fact that the goal is almost identical with what I think to be the goal
> >for Avalon. Maybe it would be a better idea to make avalon work and join
> >it instead of creating a new project ( assuming avalon people are open to
> >this ).
>
> Yes it is looking more and more like Avalon ;) I suspect that everyone in
> Avalon would be happy to see something like this happen. However at the
> moment we are trying to stabilize Avalon and adding more alpha code to the
> mix would not be appreciated ;)
Why would it be a 'mix'? This is what I don't understand about Avalon -
why isn't the DBCP separate? If Avalon is a repository of *independant*
things, I should be able to add a new piece , and users should be able
to build a al :
build.sh <target>
and get a nice little jar with only that component...
>
> So what I would be interested in doing would be to ask the PMC to allow us
> to create a new CVS (jakarta-avalon-catalog or something). This would be
> the place to burn through all the ideas and see where it leads. At the
> point where the project could stand on it's own two feet I would like to
> see it spun off into it's own project and avalons charter amended to
> exclude the new catalog library.
Sounds fine by me, as long as that notion of components as components
(i.e. separate) is there..
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
