Just one addition, we use in Cocoon namespaces a la "apache.org/cocoon",
so the directory structure should look like this I think:
/src
/blocks
/apache.org
/cocoon
/jakarta
Carsten
> -----Original Message-----
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 31, 2004 2:21 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Kernel...
>
> Pier Fumagalli wrote:
> >
> > On 31 Mar 2004, at 12:21, Carsten Ziegeler wrote:
> >
> > > I would say: yes, add the blocks directory. It would be
> good if the
> > > blocks you add there are not already used in the cocoon-2.1
> > cvs, which
> > > means just use unused names.
> >
> > Given that any block follows a naming such as
> > http://host/name/version, I would think that to avoid
> complications,
> > we could represent that structure in CVS:
> >
> > /src
> > /blocks
> > /cocoon.apache.org
> > /block_name
> > /jakarta.apache.org (???)
> > /block_name
> > /www.orixo.com (???)
> > /block_name
> >
> > And versions are ignored as CVS already provides versioning.
> >
> +1
>
> > Or would "our" block only be http://cocoon.apache.org/ even if we
> > "wrap" stuff from other people? (I'm thinking about Jakarta Commons
> > DBCP and POOL right now, maybe more stuff in the future)
> >
> Even if it will turn out later that we only have "c.a.o"
> blocks, it's easier to go the more verbose way now and don't
> have to change anything later on if we have others as well.
>
> Carsten
>
>
