cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: Status new Cocoon documentation
Date Tue, 15 Feb 2005 11:55:24 GMT
Upayavira wrote:
> David Crossley wrote:
> >
> >Here is one thing that i cannot grasp yet:
> >How will the automatically generated "Sitemap Component Documentation"
> >(i.e. the old /userdocs/) fit in with these static repositories?
> >Currently we need to run 'build docs' to prepare them, then do 'forrest'.
> >http://cocoon.apache.org/2.1/plan/review-sitemap-docs.html
> 
> How is it done now on Brutus? Isn't there a hook within Forrest to call 
> Cocoon's "build docs" before building the site? That way, the automatic 
> enhancement of the docs is always done on top of whatever is in the new 
> repository, much as it is now.
> 
> Have I missed something?

That is correct - the forrestbot is doing what you say.

At the moment i have a wrapper shell script that first does an svn update
of Cocoon's java sources and core blocks, calls 'build docs', then the
forrestbot takes over. That works but is cumbersome.

Evidently forrestbot itself could call Cocoon's 'docs' ant target prior
to starting. I am working during spare time to get that happening,
as there are various glitches.

The trouble that i have with the new documentation proposal is that
docs sources are moving to another part of the repository, so how
will 'build docs' be able to access them? I suppose that assumed default
relative pathnames with lots of dot-dots.

--David

Mime
View raw message