I just read what I wrote and it didn't make a lot of sence - its way too late and I've been up too long.
What I mean to say was that the CVS version of the build has been updated so that cocoon build first, then the javadocs target generates the missing content.
Gary Shea wrote:
On Tue, 12 Nov 2002, at 02:24 [+0100], Stephen McConnell ([EMAIL PROTECTED]:That what was seeing - but I don't understand why Cocoon generates the warning and overrites the index.html if the javadoc exists. But the guy who knows the answer to this is Ken.
Gary:On closer examination (although still not so close that I can say for
I just checking into the problem you meantioned concerning the docs
target. I've switched the javadoc and cocoon docs generation order
around so that javadoc get generated after the cocoon docs. You still
get the missing doc link - but the file its looking for is not generated
in the Javadocs phase.
IOW ignore update from CVS and invoke the docs target again and you
should get a perfectly good set of docus in the build/docs directory.
Cheers, Steve.
sure!) it appears that xdocs stuff gets copied into a 'working'
directory for cocoon, and then cocoon either outputs to the docs
directory or the cocoon output is copied there. In either case, since
the api/index.html and ../index.html aren't referred to, but are
un-available in the working directory, placeholders get made for them
which overwrite or are copied over the correct files.
Ken ... ?
Cheers, Steve.
Gary
Stephen McConnell wrote:
Gary Shea wrote:--
Yo Steve,Yep - but I though that was only because I have some strage setting in
I am seeing [broken link] messages while building both meta and assembly
docs. In each case, ../index.html and api/index.html are missing. Are
you seeing it also?
my local configuration. There is something odd that happens during the
Cocoon generation - the index.html file for the javadoc API can be
overriden for some reason that I have not figured out. What I do
locally is to generate the Javadoc to a logical place on my local
system - then I generate the xdocs target (the Cocoon stuff) and copy
the result files to my on-line content directory.
I know it could do with some optimization.
Cheers, Steve.
Gary
--
To unsubscribe, e-mail:
<mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail:
<mailto:avalon-users-help@;jakarta.apache.org>
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:mcconnell@;osm.net
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
-- Stephen J. McConnell
OSM SARL digital products for a global economy mailto:mcconnell@;osm.net http://www.osm.net -- To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
