forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-246) Lucene search complains missing docs which definitely do not exist
Date Mon, 31 Jan 2005 23:43:17 GMT
The following comment has been added to this issue:

     Author: Florian G. Haas
    Created: Mon, 31 Jan 2005 5:42 PM
This behavior is due to several factors:

* First and foremost, an error in book2cinclude-lucene.xsl which butchered filenames with
more than one dot (.) in them. This is why the relative URL howto-v13.dtdx.html is not interpreted
correctly and the Lucene facility expects to find a file named howto-v13.xml, which it of
course doesn't.

* Secondly, still pertaining to the docs in "docs-author", a mixup in priorities in the sitemap.xmap.
Any file with "images" in the filename is thus missed by the Lucene indexer.

* Thirdly, WRT the docs in "site-author", the fact that there are some entries in site.xml
which don't have any corresponding filenames, namely, the menu items /docs/ and /docs-dev/.
I have no idea how to have this handled properly by the Lucene indexer. Any help would be
dearly appreciated.

Sorry it took so long to tackle this issue. I seem not to have properly received the notification
message back in August, and I just now spotted the entry on the issue tracker.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: FOR-246
    Summary: Lucene search complains missing docs which definitely do not exist
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Forrest
             Core operations

   Reporter: David Crossley

    Created: Thu, 5 Aug 2004 8:17 AM
    Updated: Mon, 31 Jan 2005 5:42 PM

Lucene search fails with "SourceNotFoundException: file:/...src/documentation/content/xdocs/docs/howto-v13.xml
doesn't exist". However that document should not exist, so the Lucene indexer is mistakenly
being told to read bad URIs.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message