Remove configuration files from content directory

Hi all,

I would suggest to alter the directory structure
so that publication-specific configuration files
are not placed in the content directory. This has
a low priority, but if you agree, it could be
solved quite fast using global search.

Motivation:

- It is confusing to put them in the content
   directory.
- We would have a common location for all
   configuration files.

My suggestion is to create a directory named

   config

inside the publication directory and move the
files there.

The question is how much effort this takes.

tasks.xconf
- some Java files

lucene.xconf, crawler.xconf
- crawl_and_index.xml build file
- search XSP

publication.xconf
- publisher and exporter classes
- ?

I would implement all changes for the tasks.xconf
file and maybe the lucene and crawler files.

Another question is how to distinguish between
content / configuration / resources, e.g. regarding
the scheduler jobs dump file (it seems to be similar
to the search index - so is it a resource?).

Andreas