</properties>
	<profiles>
		<profile>
			<id>build</id>
			<activation>
				<activeByDefault>true</activeByDefault>
			</activation>
			<properties>
				<test.include.path>**/*Test.java</test.include.path>
				<test.command.args>--illegal-access=permit</test.command.args>
			</properties>
		</profile>
		<profile>
			<id>integrationTests</id>
			<properties>

      <outputDirectory>bin</outputDirectory>
      <includes>
        <include>mvn</include>
        <include>mvnDebug</include>
        <!-- This is so that CI systems can periodically run the profiler -->
        <include>mvnyjp</include>
      </includes>
      <lineEnding>unix</lineEnding>
      <fileMode>0755</fileMode>
    </fileSet>
    <fileSet>
      <directory>src/assembly/maven/conf</directory>

  <artifactId>parent</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-4034</name>
  <description>
    Verify that dependencies defined in profiles are subject to the dependency management of the parent.
  </description>

  <modules>
    <module>sub</module>
  </modules>

  <dependencyManagement>
    <dependencies>
      <dependency>

  <artifactId>child</artifactId>
  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-2174</name>
  <description>
    Verify that plugin dependencies defined by plugin management of a parent profile are not lost when the
    parent's main plugin management section is also present.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<profiles version="12">
<profile kind="CodeFormatterProfile" name="DBFlute Style" version="12">
<setting id="org.eclipse.jdt.core.formatter.insert_space_after_ellipsis" value="insert"/>
<setting id="org.eclipse.jdt.core.formatter.insert_space_after_comma_in_enum_declarations" value="insert"/>
<setting id="org.eclipse.jdt.core.formatter.insert_new_line_in_empty_annotation_declaration" value="insert"/>

                </configuration>
              </reportSet>
            </reportSets>
          </plugin>
        </plugins>
      </reporting>
    </profile>

    <profile>
      <id>inactiveProfile</id>
      <properties>
        <prop-inactive>||${project.basedir}||</prop-inactive>
      </properties>
      <reporting>
        <plugins>

          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

  <profiles>
    <profile>
      <id>test-1</id>
      <activation>
        <jdk>[1.4,)</jdk>
      </activation>
      <properties>
        <jdkProperty1>PASSED</jdkProperty1>
      </properties>
    </profile>
    <profile>
      <id>test-2</id>
      <activation>
        <jdk>(,100)</jdk>
      </activation>

  <artifactId>construct</artifactId>
  <version>1.0</version>
  <packaging>pom</packaging>

  <profiles>
    <profile>
      <id>dist</id>
      <modules>
        <module>maven-inherit-plugin</module>
        <module>maven-pax-plugin</module>
      </modules>
    </profile>
    </profiles>

  <description>
    Test that multiple plugin 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>
      <pluginRepositories>
        <pluginRepository>
          <id>one</id>
          <url>https://repo1.maven.org/maven2</url>
        </pluginRepository>

      <groupId>org.junit.jupiter</groupId>
      <artifactId>junit-jupiter-api</artifactId>
      <version>5.10.1</version>
      <scope>test</scope>
    </dependency>
  </dependencies>

  <profiles>
    <profile>
      <id>release</id>
      <properties>
        <prop>foo</prop>
      </properties>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>