<description>A preferred alternative to this expression, in the case where it's deprecated.</description>
          <type>String</type>
        </field>
        <field>
          <version>1.0.0</version>
          <name>ban</name>
          <description>A preferred alternative to this expression, in the case where it's banned from use.</description>
          <type>String</type>
        </field>

        <artifactId>maven-it-plugin-a</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <!-- NOTE: Explicitly reference "default" id here -->
            <id>default</id>
            <phase>child-default</phase>
          </execution>
          <execution>
            <id>non-default</id>
            <phase>child-non-default</phase>

            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
            full dependency resolution might fail due to projects which haven't been built yet.
          </description>
        </field>
        <field>
          <name>dependencyCollection</name>

            <phase>validate</phase>
            <goals>
              <goal>log-string</goal>
            </goals>
          </execution>
          <execution>
            <!-- NOTE: <id> deliberately omitted here! -->
            <phase>validate</phase>
            <goals>
              <goal>log-string</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

    <!-- javax.inject (JSR-330) -->
    <exportedPackage>javax.inject.*</exportedPackage>
    <!-- javax.enterprise.inject (JSR-299): Must never be exported if needed at plugin level, plugin adds it
         there is no justification to get it at Maven level and leaking it will conflict.
    <exportedPackage>javax.enterprise.util.*</exportedPackage>
    <exportedPackage>javax.enterprise.inject.*</exportedPackage>
    -->

   |
   | For example, if you have an integration testing plugin - like cactus - that needs to know where
   | your Tomcat instance is installed, you can provide a variable here such that the variable is
   | dereferenced during the build process to configure the cactus plugin.
   |

          <artifactId>maven-it-plugin-a</artifactId>
          <version>2.1-SNAPSHOT</version>
          <executions>
            <execution>
              <!-- NOTE: Implicitly reference "default" id here, i.e. omit the <id> element -->
              <phase>parent-default</phase>
            </execution>
            <execution>
              <id>non-default</id>
              <phase>parent-non-default</phase>

        <artifactId>maven-it-plugin-a</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <!-- NOTE: Implicitly reference "default" id here, i.e. omit the <id> element -->
            <phase>parent-default</phase>
          </execution>
          <execution>
            <id>non-default</id>
            <phase>parent-non-default</phase>
          </execution>

         its builds. Thus, GWT doesn't get j2objc-annotations transitively, in
         contrast to the other deps of `guava`, which it does get transitively.
         (Arguably we should redeclare *all* the `guava` deps here.) -->
    <dependency>
      <groupId>com.google.j2objc</groupId>
      <artifactId>j2objc-annotations</artifactId>
    </dependency>
    <dependency>
      <groupId>com.google.guava</groupId>

  </ciManagement>
  <modules>
    <module>guava</module>
    <module>guava-bom</module>
    <module>guava-testlib</module>
    <module>guava-tests</module>
  </modules>
  <build>
    <!-- Handle where Guava deviates from Maven defaults -->
    <sourceDirectory>src</sourceDirectory>
    <testSourceDirectory>test</testSourceDirectory>
    <resources>
      <resource>
        <directory>../..</directory>
        <includes>