<name>ExpressionDocumentation</name>
      <description>The root of a parameter plugin expression document.</description>
      <fields>
        <field>
          <version>1.0.0</version>
          <name>expressions</name>
          <description>The list of plugin parameter expressions described by this
            document.</description>
          <association>
            <type>Expression</type>

   | dereferenced during the build process to configure the cactus plugin.
   |
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a property, either matching a particular value for the property,

<?xml version="1.0" encoding="UTF-8"?>
<OpenSearchDescription xmlns="http://a9.com/-/spec/opensearch/1.1/">
  <ShortName>Fess</ShortName>
  <Description>Full Text Search for Your Documents.</Description>
  <Tags>Full Text Search</Tags>
  <Contact>******@****.***</Contact>
  <SearchForm>http://localhost:8080/fess/</SearchForm>
  <Url type="text/html" template="http://localhost:8080/fess/search?q={searchTerms}"/>
  <InputEncoding>UTF-8</InputEncoding>

   | way you don't have to hardcode paths in your pom.xml.
   |
   | Every toolchain consist of 3 elements:
   | * type: the type of tool. An often used value is 'jdk'. Toolchains-aware
   |   plugins should document which type you must use.
   |
   | * provides: A list of key/value-pairs.
   |   Based on the toolchain-configuration in the pom.xml Maven will search for

		<property name="generatorList">
			["${path}/generate-thumbnail"]
		</property>
		<postConstruct name="addCondition">
			<arg>"mimetype"</arg>
			<arg>"application/vnd.openxmlformats-officedocument.wordprocessingml.document"</arg>
		</postConstruct>
		<postConstruct name="addCondition">
			<arg>"mimetype"</arg>
			<arg>"application/vnd.openxmlformats-officedocument.spreadsheetml.sheet"</arg>
		</postConstruct>

		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.bad_word/bad_word"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.boost_document_rule/boost_document_rule"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.crawling_info/crawling_info"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">

          <type>String</type>
          <!-- This default has to be enforced at the maven-artifact layer, to allow
            | injection of defaults from <dependencyManagement/>.
            | TODO: how can we document it?
            |-->
          <!-- defaultValue>compile</defaultValue -->
        </field>
        <field>
          <name>systemPath</name>
          <version>4.0.0+</version>
          <description>

<?xml version="1.0" encoding="UTF-8"?>
<OpenSearchDescription xmlns="http://a9.com/-/spec/opensearch/1.1/">
  <ShortName>Fess</ShortName>
  <Description>Full Text Search for Your Documents.</Description>
  <Tags>Full Text Search</Tags>
  <Contact>******@****.***</Contact>
  <SearchForm>http://localhost:8080/fess/</SearchForm>
  <Url type="text/html" template="http://localhost:8080/fess/search?q={searchTerms}"/>
  <InputEncoding>UTF-8</InputEncoding>