<postConstruct name="addDesignJspFileName">
			<arg>"newpassword"</arg>
			<arg>"login/newpassword.jsp"</arg>
		</postConstruct>
		<postConstruct name="addDesignJspFileName">
			<arg>"profile"</arg>
			<arg>"profile/index.jsp"</arg>
		</postConstruct>
	</component>
	<component name="crawlingInfoHelper" class="org.codelibs.fess.helper.CrawlingInfoHelper">
	</component>

        <groupId>org.codehaus.mojo</groupId>
        <artifactId>cobertura-maven-plugin</artifactId>
        <version>2.2</version>
      </plugin>
    </plugins>
  </reporting>

  <profiles>
      <profile>
          <id>internal-catalog</id>
          <build>
              <plugins>
                  <plugin>
                      <groupId>org.apache.maven.plugins</groupId>

    <exportedArtifact>org.apache.maven:maven-plugin-parameter-documenter</exportedArtifact>
    <exportedArtifact>org.apache.maven:maven-plugin-registry</exportedArtifact>
    <exportedArtifact>org.apache.maven:maven-profile</exportedArtifact>
    <exportedArtifact>org.apache.maven:maven-project</exportedArtifact>
    <exportedArtifact>org.apache.maven:maven-repository-metadata</exportedArtifact>

          </plugin>
          <plugin>
            <artifactId>only-active-profile</artifactId>
            <executions>
              <execution>
                <id>Active only ||${project.basedir}||</id>
                <configuration>
                  <plugin-in-active-profile-only>Active only ||${project.basedir}||</plugin-in-active-profile-only>
                </configuration>
              </execution>

          <version>2.1-SNAPSHOT</version>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

  <profiles>
    <profile>
      <!-- NOTE: This test injects the plugin configuration via a profile -->
      <id>maven-core-it</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
      <build>
        <plugins>
          <plugin>

  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-4107</name>
  <description>
    Test that POM interpolation uses the property values from the dominant profile source (POM vs. settings.xml).
    This boils down to the proper order of profile injection and interpolation, i.e.
    interpolate after profiles from all sources are injected.
  </description>

  <properties>

        </configuration>
      </plugin>
    </plugins>
  </build>

  <profiles>
    <profile>
      <!-- an active but empty profile to ensure profile injection does not interfere with plugin configuration -->
      <id>parent</id>
      <activation>
        <activeByDefault>true</activeByDefault>
      </activation>
    </profile>
  </profiles>

  <description>
    Test that multiple artifact repository declarations with the same id cause a validation error even if the
    repositories are defined within a (non-active) profile.
  </description>

  <profiles>
    <profile>
      <id>test</id>
      <repositories>
        <repository>
          <id>one</id>
          <url>https://repo1.maven.org/maven2</url>
        </repository>
        <repository>

    <module>module-1</module>
    <module>module-3</module>
  </modules>
  <profiles>
    <profile>
      <id>a</id>
      <properties>
        <b>test-prop</b>
      </properties>
      <modules>
        <module>module-1</module>
        <module>module-4</module>
      </modules>
    </profile>
  </profiles>

        automatic inclusion of the build profile. Multiple conditions can be defined, which must
        be all satisfied to activate the profile.
      </description>
      <fields>
        <field>
          <name>activeByDefault</name>
          <version>4.0.0+</version>
          <type>boolean</type>
          <description>If set to true, this profile will be active unless another profile in this