<version>1.0.0/1.1.0</version>
          <type>String</type>
          <description>
            Flags this Mojo as requiring information about the dependencies that would make up the specified class
            path. As the name suggests, this is similar to requiresDependencyResolution and supports the same values.

      <releases>
        <!-- That's the boolean POM field we would like to interpolate -->
        <enabled>${releasesEnabled}</enabled>
      </releases>
    </repository>
  </repositories>

  <build>
    <resources>
      <resource>
        <directory>src/main/resources</directory>
        <!-- That's the boolean POM field we would like to interpolate -->
        <filtering>${filter.resources}</filtering>

        <configuration>
          <excludes>
            <!-- Yes, we want to exclude ForceGuavaCompilation 4 times: -->
            <!-- (And we might as well exclude DummyJavadocClass 3 times (though it would be harmless to include).) -->
            <!-- 1. Don't compile it (since that requires a *non-test* dep on gwt-user. -->
            <exclude>**/ForceGuavaCompilation*</exclude>
            <exclude>**/DummyJavadocClass*</exclude>

    <exportedArtifact>org.eclipse.aether:aether-connector-basic</exportedArtifact>

    <!--
      | NOTE: Don't exclude the wagons or any of their dependencies (apart from the wagon API). This would otherwise
      | provoke linkage errors for wagons contributed by build extensions. We also don't need to exclude the wagons

  <name>Maven Integration Test :: MNG-3900</name>
  <description>
    Test that build properties defined via active profiles are used for
    interpolation.
  </description>

  <!--
    These are some POM elements we would like to interpolate with
    properties from the profile.
  -->
  <url>https://maven.apache.org/${test}
  </url>
  <properties>
    <test>FAILED</test>
    <property>${test}</property>
  </properties>

			<arg>"fess_config.duplicate_host/duplicate_host"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.elevate_word/elevate_word"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.elevate_word_to_label/elevate_word_to_label"</arg>
		</postConstruct>
		<postConstruct name="addIndexConfig">
			<arg>"fess_config.failure_url/failure_url"</arg>
		</postConstruct>

            Toolchain identification information, which will be matched against project requirements.
            <p>For Maven 2.0.9 to 3.2.3, the actual content structure was completely open: each toolchain type would
            define its own format and semantics. This was generally a properties format.
            <p>Since Maven 3.2.4, the type for this field has been changed to Properties to match the de-facto
            format.

    formed by whitespace-only events must be retained.
    -->
    <prop1><!-- X -->That's<!-- X --> <!-- X -->a<!-- X --> <!-- X -->test!<!-- X --></prop1>

    <!--
    This checks the coalescing of CHARACTERS events which would otherwise be reported in chunks of the internal parser
    buffer size (usually 4 or 8 KB). The text block is designed such that its length is exactly 32 KB after leading

              <url>https://docs.oracle.com/javase/9/docs/api/</url>
              <location>https://docs.oracle.com/javase/9/docs/api/</location>
            </offlineLink>
            <!-- The Checker Framework likewise would claim javax.annotations, despite providing only a subset of the JSR305 annotations, so it must likewise come after JSR305. -->
            <offlineLink>
              <url>https://checkerframework.org/api/</url>

  |
  | o add specification element to a field, this would be more a technical description of
  |   what is allowed in the field.
  |
  | o validators: there could be several levels of validation. Simple type validation could
  |   be done with a regex, but we need inter-field validation and rules which could be
  |   dealt with by something like drools.
  |
  | o i18n: would be good to be able to have names/descriptions/specifications