Make mime types and file extentions configurable per project

Some mime types and file extensions can be handled by multiple
formatters, e.g. there can be two different formatters for Markdown.
By allowing projects to configure mime types and file extensions for
formatters each project can decide which formatter should be used.
E.g. if globally the following Markdown formatter is configured

  [formatter "MARKDOWN"]
    mime-type = text/x-markdown

a project may overwrite this by having the following configuration in
a 'xdocs.config' file in its refs/meta/config branch:

  [formatter "FANCY_MARKDOWN"]
    mime-type = text/x-markdown
  [formatter "MARKDOWN"]

Formatter configurations are inherited from parent projects.

Being able to configure file extensions on project level is also
useful if projects use different file extensions for one format. E.g.
some projects my use *.adoc files for asciidoc documentation and other
projects may use *.txt for asciidoc documentation.

Change-Id: I5b095ab4c697d8367f3ddd421312fd59ca6a4051
Signed-off-by: Edwin Kempin <edwin.kempin@sap.com>
5 files changed
tree: 3359ec0b0cd119e82a2094eb42c4f9cc47b8fa9b
  1. .settings/
  2. lib/
  3. src/
  4. .buckconfig
  5. .gitignore
  6. BUCK
  7. LICENSE
  8. pom.xml
  9. VERSION