return types -->
							<className>**</className>
							<differenceType>7006</differenceType>
							<method>*</method>
							<from>*</from>
							<to>*</to>
						</difference>
						<difference>
							<className>jcifs/Configuration</className>
							<differenceType>7012</differenceType>
							<method>boolean isSendNTLMTargetName()</method>

    comprehension tool. Based on the concept of a project object model:
    builds, dependency management, documentation creation, site
    publication, and distribution publication are all controlled from
    the declarative file. Maven can be extended by plugins to utilise a
    number of other development tools for reporting or the build
    process.
  </description>
  <url>http://maven.apache.org/</url>

    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-model</artifactId>
    </dependency>
    <!-- Remove the following two deps to see how to remove Settings from the core -->
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-settings</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven</groupId>

            <groupId>org.apache.maven.its</groupId>
            <artifactId>a</artifactId>
            <!-- version from BOM -->
        </dependency>
    </dependencies>

    <build>
        <plugins>
            <plugin>
                <artifactId>maven-clean-plugin</artifactId>
                <!-- version from parent -->
            </plugin>
        </plugins>
    </build>

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.tests</groupId>
  <artifactId>build-from-file</artifactId>
  <version>1</version>

specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <!--
  This (almost) minimal POM tests direct inheritance from the super POM.
  -->

  <groupId>org.apache.maven.its.mng3843</groupId>
  <artifactId>test-1</artifactId>
  <version>0.1</version>

  <name>test</name>

  <build>
    <plugins>
      <plugin>

  <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>

  <profiles>
    <profile>

  <packaging>JAR</packaging>

  <name>Maven Integration Test :: MNG-4332</name>
  <description>
    Verify that default plugin executions contributed by the packaging are executed before user-defined
    executions from the POM's build section, regardless whether the executions are defined in the regular
    plugins section or the plugin management section.
  </description>

  <build>
    <pluginManagement>
      <plugins>

    </dependency>
  </dependencies>
  <build>
    <resources>
      <resource>
        <directory>..</directory>
        <includes>
          <include>LICENSE</include> <!-- copied from the parent pom because I couldn't figure out a way to make combine.children="append" work -->
          <include>proguard/*</include>
        </includes>
        <targetPath>META-INF</targetPath>
      </resource>

      <artifactId>guava</artifactId>
      <version>${project.version}</version>
    </dependency>
    <!-- We redeclare the j2objc-annotations dependency from `guava`: Our Gradle
         Module Metadata hides the dependency declared in `guava` from runtime
         configurations downstream, and GWT uses the runtime configuration for
         its builds. Thus, GWT doesn't get j2objc-annotations transitively, in