<artifactId>maven-it-plugin-log-file</artifactId>
        <version>2.1-SNAPSHOT</version>
      </plugin>
      <plugin>
        <!-- NOTE: It's essential that this plugin is also referenced by the default lifecycle bindings -->
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-resources-plugin</artifactId>
        <version>0.1-stub-SNAPSHOT</version>
      </plugin>

            this case, you want the user to modify {@code <build><finalName/></build>} rather
            than specifying a value for finalName directly in the plugin configuration section. It is also useful to
            ensure that - for example - a List-typed parameter which expects items of type Artifact doesn't get a List
            full of Strings.
          </description>
        </field>
        <field>

    <!--
      | MNG-6240: Plugins might depend on maven-aether-provider <= 3.3.9 before the rename to maven-resolver-provider.
      | Since backwards-compatibility was kept, Maven Core also provides this artifact.
     -->
    <exportedArtifact>org.apache.maven:maven-aether-provider</exportedArtifact>
    <exportedArtifact>org.apache.maven:maven-resolver-provider</exportedArtifact>

            In particular this includes all subpackages. Despite the element name one can also only expose individual classes of a particular package by adding its binary name as value.
          ]]></description>
        </field>
        <field>
          <name>exportedArtifacts</name>

    <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>
      <syntax>settings.interactiveMode</syntax>
      <configuration>

  <version>1.0</version>
  <name>Guava ListenableFuture only</name>
  <description>
    Contains Guava's com.google.common.util.concurrent.ListenableFuture class,
    without any of its other classes -- but is also available in a second
    "version" that omits the class to avoid conflicts with the copy in Guava
    itself. The idea is:

    - If users want only ListenableFuture, they depend on listenablefuture-1.0.

  <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>
        <artifactId>maven-it-plugin-class-loader</artifactId>
        <executions>

  <version>9999.0-empty-to-avoid-conflict-with-guava</version>
  <name>Guava ListenableFuture only</name>
  <description>
    An empty artifact that Guava depends on to signal that it is providing
    ListenableFuture -- but is also available in a second "version" that
    contains com.google.common.util.concurrent.ListenableFuture class, without
    any other Guava classes. The idea is:

          <version>3.0.0+</version>
          <description>
            The roles the contributor plays in the project. Each role is described by a
            {@code role} element, the body of which is a role name. This can also be used to
            describe the contribution.
          </description>
          <association>
            <type>String</type>
            <multiplicity>*</multiplicity>
          </association>

   |
   | * configuration: Additional configuration for this tool.
   |   Look for documentation of the toolchains-aware plugin which configuration elements
   |   can be used.
   |
   | See also https://maven.apache.org/guides/mini/guide-using-toolchains.html
   |
   | General example

  <toolchain>
    <type/>
    <provides>
      <version>1.0</version>
    </provides>
    <configuration/>