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
            want to analyze the set of transitive dependencies, in particular during early lifecycle phases where

        <field xdoc.separator="blank">
          <name>parent</name>
          <version>4.0.0+</version>
          <description>The location of the parent project, if one exists. Values from the parent
            project will be the default for this project if they are left unspecified. The location
            is given as a group ID, artifact ID and version.</description>
          <association>
            <type>Parent</type>

    <exportedPackage>javax.enterprise.inject.*</exportedPackage>
    -->

    <!-- javax.annotation (JSR-250) -->
    <exportedPackage>javax.annotation.*</exportedPackage>
    <exportedPackage>javax.annotation.security.*</exportedPackage>

    <exportedPackage>jakarta.inject.*</exportedPackage>
    <exportedPackage>jakarta.annotation.*</exportedPackage>

    <!--

        repository.</description>
      <cliOptions>
        <cliOption>
          <key>-Dmaven.repo.local=/path/to/local/repo</key>
          <value>Override the local repository location on a per-build basis.</value>
        </cliOption>
      </cliOptions>
    </expression>
    <expression>
      <syntax>reactorProjects</syntax>
      <description>This is the current list of projects being built by

    </description>
  </expression>
  <expression>
    <syntax>project.file</syntax>
    <description> This is the File instance that refers to the location of the current POM on
      disk.
    </description>
  </expression>
  <expression>
    <syntax>project.artifacts</syntax>
    <configuration>
      <![CDATA[
<dependencies>
  ...
</dependencies>

 |
 |  1. User Level. This toolchains.xml file provides configuration for a single user,
 |                 and is normally provided in ${user.home}/.m2/toolchains.xml.
 |
 |                 NOTE: This location can be overridden with the CLI option:
 |
 |                 -t /path/to/user/toolchains.xml
 |
 |  2. Global Level. This toolchains.xml file provides configuration for all Maven

  <name>MavenToolchains</name>
  <description><![CDATA[
    This is a reference for the Maven Toolchains descriptor.
    <p>The default location for the toolchains file is {@code ~/.m2/toolchains.xml}
    <p>A Toolchain is a preconfigured object that Maven plugins can use for tool configuration retrieval (location and other information).
    <p>The <a href="/plugins/maven-toolchains-plugin/">toolchains-plugin</a> can read available toolchains on the user's computer

    <modelVersion>4.0.0</modelVersion>

    <parent>
        <groupId>org.apache.maven.its</groupId>
        <artifactId>parent</artifactId>
        <version>0.1</version>
    </parent>

    <artifactId>location-tracking</artifactId>
    <packaging>jar</packaging>

    <repositories>
        <repository>
            <id>remote-repo</id>
            <url>file://${basedir}/../../src/test/remote-repo</url>
        </repository>

  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-2006</name>
  <description>
    Test that inheritance of those URLs which automatically append the child's artifact id take the child's
    relative location to the parent into account.
  </description>

  <modules>
    <module>../child</module>
  </modules>

  <url>https://project.url/parent</url>

  <scm>
    <url>https://viewvc.project.url/parent</url>

  </parent>

  <artifactId>child</artifactId>
  <name>Child Project</name>
  <description>
    Test that inheritance of those URLs which automatically append the child's artifact id take the child's
    relative location to the parent into account.
  </description>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-expression</artifactId>