xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  some garbage maven project builder can't parse

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

      | to be made available to plugin authors. If we find people are getting fancy and want to take advantage of
      | Guice specifics we can expose that later. Really some testing needs to be done to see full hiding
      | of Guice has any impact on what we may categorize as a standard JSR-330 based Tesla/Maven plugin.

        <exportedPackage>com.google.inject.*</exportedPackage>

      <executionStrategy>once-per-session</executionStrategy>
      <deprecated>deprecated-mojo</deprecated>
      <since>2.2</since>
      <executePhase>generate-sources</executePhase>
      <executeGoal>some-goal</executeGoal>
      <executeLifecycle>cobertura</executeLifecycle>
      <configurator>antrun</configurator>
      <parameters>
        <parameter>
          <name>finalName</name>
          <alias>jarName</alias>

    <version>1</version>
  </parent>

  <groupId>org.apache.maven.validation</groupId>
  <artifactId>project</artifactId>
  <version>1.0.0-SNAPSHOT</version>

  <properties>
    <x>just/some/path</x>
  </properties>

  <repositories>
    <repository>
      <id>repo</id>
      <url>file://${x}/sdk/maven/repo</url>
    </repository>
  </repositories>

  <name>Maven Integration Test :: MNG-4116</name>
  <description>
    Test that the project builder does not decode URLs (which must be done by the transport layer instead).
  </description>

  <!-- some URLs using percent-encoded characters -->
  <url>https://maven.apache.org/spacy%20path</url>
  <scm>
    <connection>scm:svn:svn+ssh://svn.apache.org/spacy%20path</connection>

     *
     * @return The POM file from which this model originated or {@code null} if this model does not belong to a local
     *         project (e.g. describes the metadata of some artifact from the repository).
     */
    @Deprecated
    public java.io.File getPomFile() {
        return (getDelegate().getPomFile() != null) ? getDelegate().getPomFile().toFile() : null;
    }

    precisely control parts of the extension and dependencies to expose in the API class loader.
    Maven uses Plexus Classworlds to build the class loader hierarchy, therefore some concepts used in this extensions
    stem from Plexus Classworlds originally.
    <p><i>Notice:</i> this documentation is generated from a Modello model but the code executed is not generated

    </dependency>
    <dependency>
      <groupId>org.apache.maven.resolver</groupId>
      <artifactId>maven-resolver-transport-file</artifactId>
    </dependency>
    <!-- HTTP/1.1, lowest priority, Java8+ (still must as some ITs force it) -->
    <dependency>
      <groupId>org.apache.maven.resolver</groupId>
      <artifactId>maven-resolver-transport-wagon</artifactId>
    </dependency>
    <!-- HTTP/1.1, medium priority, Java8+ -->

                        <configuration>
                            <fail>true</fail>
                            <rules>
                                <requireMavenVersion>
                                    <!-- Some plugin features require a recent Maven runtime to work properly -->
                                    <message>Current version of Maven ${maven.version} required to build the project