It was a weird behaviour of my system. The problem stands resolved. I find search.xmap in webapp directory. However the object of me touching search.xmap is still unresolved. I'm trying to make Lucene search and index the raw HTML files (all raw html files and folders are placed in a folder globaljavadocs under content). What could be wrong with the following code?
 
      <!-- Creates a lucene:document from a Forrest document body -->
      <map:match pattern="**body-*.lucene">
     
        <map:select type="exists">
         
          <map:when test="{project:content.globaljavadocs}{1}{2}.ehtml">
            <map:generate type="html" src="" />
            <map:transform src="" />
          </map:when>
         
          <map:when test="{project:content.xdocs}{1}{2}.ehtml">
            <map:generate src="" />
            <map:transform src="" />
          </map:when>
          <map:when test="cocoon://{1}{2}.xml">
            <map:generate src=""
          </map:when>
        </map:select>
        <map:transform src="">          <map:parameter name="document-url" value="{1}{2}.xml"/>
        </map:transform>
        <map:serialize type="xml"/>
      </map:match>

      <!-- Creates a lucene:document from a Forrest document (same as
      above, as search-relevant information is only contained in the
      body) -->
      <map:match pattern="*.lucene">
        <map:generate src="">        <map:serialize type="xml"/>
      </map:match>

      <map:match pattern="**/*.lucene">
        <map:generate src="">        <map:serialize type="xml"/>
      </map:match>


Thanks and regards,
Karthik.
 
On 11/13/05, Ross Gardler <[EMAIL PROTECTED]> wrote:
Karthik Manimaran wrote:

> Deleting search.xmap in build directory seems to have no effect on
> Lucene search (it still works fine) and so does modifying/adding new
> pipeline in search.xmap. Any reasons?


What build directory are you finding search.xmap? The core XMaps are
used in-place and should not be in any build directory.

Ross