I tried to build the docs inside trunk and also the docs in the site
(https://svn.apache.org/repos/asf/lucene/java/site), which both fail to
build.

The error is the same here (Win XP), except, that it says, that it cannot
find the images (which are indeed not available).

The last time I generated the site docs for revision 784758, after that
Grant applied LUCENE-1706. Maybe he missed to commit some new images for the
lucidimagination powered search.

But from the change in broken-links.xml, I see, that Grant must have seen
the same error, but ignored it. The docs seem to be correct, so I think this
error is not fatal.

Uwe

-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [email protected]

> -----Original Message-----
> From: Michael McCandless [mailto:[email protected]]
> Sent: Tuesday, July 07, 2009 8:25 PM
> To: [email protected]
> Subject: broken links when building web-site
> 
> I'm trying to regen the web site docs (w/ forrest), for LUCENE-1522,
> but I'm hitting a "BUILD FAILED" at the end, I think because of these
> broken links:
> 
> X [0]
> images/instruction_arrow.png  BROKEN:
> /lucene/h2.1522/src/site/src/documentation/content/xdocs/images.instructio
> n_arrow.png
> (No such file or directory)
> X [0]
> skin/images/current.gif       BROKEN:
> /tango/offload/usr/local/src/apache-forrest-0.8/main/webapp/. (Is a
> directory)
> X [0]
> skin/images/chapter.gif       BROKEN:
> /tango/offload/usr/local/src/apache-forrest-0.8/main/webapp/. (Is a
> directory)
> X [0]                                     skin/images/page.gif
BROKEN:
> /tango/offload/usr/local/src/apache-forrest-0.8/main/webapp/. (Is a
> directory)
> 
> Does anyone else see this?
> 
> Mike
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to