</postConstruct>
		<postConstruct name="addDesignJspFileName">
			<arg>"header"</arg>
			<arg>"header.jsp"</arg>
		</postConstruct>
		<postConstruct name="addDesignJspFileName">
			<arg>"footer"</arg>
			<arg>"footer.jsp"</arg>
		</postConstruct>
		<postConstruct name="addDesignJspFileName">
			<arg>"search"</arg>
			<arg>"search.jsp"</arg>
		</postConstruct>
		<postConstruct name="addDesignJspFileName">

					<header>&lt;a href="https://fess.codelibs.org/" target="_blank"&gt;Enterprise Search Server: Fess&lt;/a&gt;</header>
					<footer>&lt;a href="https://fess.codelibs.org/" target="_blank"&gt;Open Source Enterprise Search Server: Fess&lt;/a&gt;</footer>
				</configuration>
			</plugin>
			<plugin>
				<artifactId>maven-jxr-plugin</artifactId>
				<configuration>

      <version>1.0</version>
      <type>jar</type>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>surefire</groupId>
      <artifactId>surefire-booter</artifactId>
      <version>1.1</version>
      <type>jar</type>
      <scope>compile</scope>
    </dependency>
    <dependency>
      <groupId>maven</groupId>
      <artifactId>wagon-api</artifactId>

          <version>3.0.0+</version>
          <description>
            This element describes all the classpath resources such as properties
            files associated with a project. These resources are often included in the final
            package.
            The default value is {@code src/main/resources}.
          </description>
          <association>
            <type>Resource</type>

   | * 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
   |   matching <provides/> configuration. You can decide for yourself which key-value
   |   pairs to use. Often used keys are 'version', 'vendor' and 'arch'. By default