> > BTW, that does save us much effort for maintaining the doc generation
> > process.
>
> that's exactly the goal.
>
> So, at the end, here is what I propose:
>
> 1) we remove all the old docs targets from the build
>
> 2) documentation will be done thru forrest. This requires forrest be
> available on the machine separately. since users won't update the
> documentation this should not be a problem.
>
> 3) we ship the pregenerated documentation in the distribution and we
> ship along the xml source files. if the documentation is included in the
> webapp cocoon will simply *read* them (not process them as right now).
>
> 4) this breaks the flow samples that depend on those stylesheets but
> they are going to be refactored anyway, so don't worry.
>
> 5) finally, remove all the doc-generation stylesheets from the CVS
>
> what do you think?

Great! +1

Stephan.

Reply via email to