Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Date: Mon, 24 Mar 2003 18:58:10 +0100 (CET)
From: Stephan Michels <stephan@apache.org>
To: cocoon-dev <cocoon-dev@xml.apache.org>
Subject: Re: [vote] Forrestizing Cocoon and more
In-Reply-To: <3E7F453B.8090009@apache.org>
Message-ID: <Pine.LNX.4.44.0303241856450.31664-100000@vern.chem.tu-berlin.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


> > 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.