cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <>
Subject Re: [vote] Forrestizing Cocoon and more
Date Tue, 25 Mar 2003 15:44:12 GMT
Stephan Michels wrote:
>>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?
> So, I have converted all xdocs to v11, and wrote a sitemap, which
> delivers the static content. But now I have the following problem that
> every time I make a webapp all docs must be rehandled :-/

just set exclude.webapp.documentation=true in your file.

> I think it is the best to separate these things complete.
> webapp -> create a webapp with samples or a clean webap.
> docs/forrest -> create the static docs.
> BTW, I see much projects, which delivers more than one webapp, perhaps
> it's a solution to offer two war's: cocoon-samples.war, cocoon-clean.war ?

Nah, the build is already configurable enough. If you don't want the 
docs (or the samples, or the javadocs or the IDLdocs) just don't include 
them in your webapp build.


View raw message