<project>
  <modelVersion>4.0.0</modelVersion>
  <parent>
    <groupId>tests</groupId>
    <artifactId>resolve-parent-pom-parent</artifactId>
    <version>1</version>
  </parent>

  <artifactId>resolve-parent-pom</artifactId>

    <configuration>
      <![CDATA[
<repositories>
  ...
</repositories>
    ]]></configuration>
    <description>
      <![CDATA[
      This is a list of ArtifactRepository instances used to resolve the Artifacts associated
      with the current POM.

      NOTE: This list will contain entries for repositories specified by ancestor POMs, including
      the default built-in super-POM, which is the parent of all POMs.

        <forkId implementation="int" default-value="-1">${forkId}</forkId>
      </configuration>
    </mojo>
    <mojo>
      <goal>resolve-late-bound-plugin</goal>
      <description>Resolve a late-bound plugin during a build, right before it is to be used.</description>
      <requiresDirectInvocation>false</requiresDirectInvocation>
      <requiresProject>false</requiresProject>

            path. As the name suggests, this is similar to requiresDependencyResolution and supports the same values.
            The important difference is this will not resolve the files for the dependencies, i.e. the artifacts
            associated with a Maven project can lack a file. As such, this annotation is meant for Mojos that only

  <description>
    Test that interpolation of properties that resolve to XML markup doesn't crash the project builder.
  </description>

  <properties>
    <!-- That's the property containing escaped XML markup -->
    <xmlMarkup>&lt;?xml version='1.0'?&gt;Tom&amp;Jerry</xmlMarkup>
    <!-- That's a property where the above property will be resolved -->
    <xmlTest>${xmlMarkup}</xmlTest>
  </properties>

      <configuration>
        <![CDATA[
    <offline>true</offline>
    ]]></configuration>
      <description>
        <![CDATA[
      Flags the system as offline, to prevent accessing the network to resolve artifacts or execute plugins.

      NOTE: It's also possible to switch to offline mode on a per-build basis, using the '-o' command-line option.
    ]]></description>
    </expression>
    <expression>

      <artifactId>maven-resolver-util</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven.resolver</groupId>
      <artifactId>maven-resolver-impl</artifactId>
    </dependency>
    <dependency>
      <groupId>org.codehaus.plexus</groupId>
      <artifactId>plexus-interpolation</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven.wagon</groupId>

        <artifactId>maven-repository-metadata</artifactId>
        <version>${project.version}</version>
      </dependency>
      <dependency>
        <groupId>org.apache.maven</groupId>
        <artifactId>maven-resolver-provider</artifactId>
        <version>${project.version}</version>
      </dependency>
      <dependency>
        <groupId>org.apache.maven</groupId>
        <artifactId>maven-settings</artifactId>

    <exportedArtifact>org.apache.maven.resolver:maven-resolver-api</exportedArtifact>
    <exportedArtifact>org.apache.maven.resolver:maven-resolver-spi</exportedArtifact>
    <exportedArtifact>org.apache.maven.resolver:maven-resolver-impl</exportedArtifact>
    <exportedArtifact>org.apache.maven.resolver:maven-resolver-util</exportedArtifact>
    <exportedArtifact>org.apache.maven.resolver:maven-resolver-connector-basic</exportedArtifact>

    <dependency>
      <groupId>org.apache.maven.resolver</groupId>
      <artifactId>maven-resolver-api</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven.resolver</groupId>
      <artifactId>maven-resolver-spi</artifactId>
    </dependency>
    <dependency>
      <groupId>org.apache.maven.resolver</groupId>
      <artifactId>maven-resolver-util</artifactId>
    </dependency>
    <dependency>