Hi,

I was just discussing with John how the module loading works now and I would
like to start a developer's guide outlining how this works so we can decide
on the final behaviour because John found a glitch in the ordering. I need
to document this better anyway.

So I wanted to nuke all the docs in HEAD because I want to start from
scratch and pull it bits from the 2.1 tree as needed. We should keep
publishing the docs from the 2.1 branch.

So I would like to

1. Nuke all the docs in HEAD and start with a developer's guide

2. I want to stop checking in generated docs, it's a PITA. I think for
for now we can use a simple rsync script to copy the docs onto the apache
machine efficiently. I'm using jon's approach of making a simple procedure
that is not ideal but we should move toward not storing generated anything
of anykind in CVS. This will only be for the HEAD docs anyway for now so it
won't really affect anyone who isn't writing 3.0 docs.

At any rate I'll make a tiny section of the developer's guide outlining the
module searching/loading order so that we can clarify this.

We can probably reimport the tree soon too as it is almost entirely cleaned
out now.

-- 

jvz.

Jason van Zyl

http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to