Sam Ruby wrote:
>
> Geir Magnusson Jr. wrote:
> >
> > So in a sense, Directory is another library project with open
> > rules (like agora). (Not sure if Agora was going to be a
> > Library peer in Jakarta-land, or a 'product peer' in Library-land.
>
> My biggest concern is that I don't understand the relationship between
> Library, Directory, Agora, and Avalon.
With the big exception of the productized components, Avalon is
completely separate from Lib, Dir, Ag. But you are right, one of the
[many :)] interpretations of Avalon could be that of hosting productized
components.
I just thought that having a directory of 'stuff' so people (internal to
Jakarta as well as, and maybe more importantly outsiders) can find
things is important - the recognition of the richness of the Jakarta
codebases is what got me started on this in the first place..
> Avalon has been in the process of splitting into multiple cvs repositories,
> using the naming convention of jakarta-avalon-xxx.
>
> It would be a simple matter to create a jakarta-avalon-dbpool.
>
I am all for jakarta-avalon-dbpool as long as its separable from Avalon
in build, documentation and independence of purpose. By this I mean that
the dbpool can primarily implement standard JDBC-compliant interfaces
and conventions, and is not required to fit into the Avalon-patterns or
framework.
I think it would be great to house it there - if avalon turns out to be
what I want library to be, you'll see me there :)
> I'd like to hear consensus with someone representing jakarta-avalon (i.e.,
> Peter Donald) before creating another subproject with overlapping goals.
>
> - Sam Ruby
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
