<groupId>maven.t02</groupId>
  <artifactId>p2</artifactId>
  <packaging>pom</packaging>
  <name>p2</name>
  <version>1.0</version>
  <mailingLists>
    <mailingList>
      <name>mailing-list</name>
    </mailingList>
  </mailingLists>

  <groupId>org.apache.maven.its.mng3843.child</groupId>
  <artifactId>child-2</artifactId>
  <version>0.2</version>
  <packaging>jar</packaging>

  <mailingLists>
    <mailingList>
      <name>child-mailing-list</name>
    </mailingList>
  </mailingLists>

      <timezone>+1</timezone>
      <properties>
        <contributor>yes</contributor>
      </properties>
    </contributor>
  </contributors>

  <mailingLists>
    <mailingList>
      <name>project-mailing-list</name>
      <subscribe>subscribe@</subscribe>
      <unsubscribe>unsubscribe@</unsubscribe>
      <post>post@</post>
      <archive>mail-archive</archive>
      <otherArchives>

      <timezone>+1</timezone>
      <properties>
        <contributor>yes</contributor>
      </properties>
    </contributor>
  </contributors>

  <mailingLists>
    <mailingList>
      <name>project-mailing-list</name>
      <subscribe>subscribe@</subscribe>
      <unsubscribe>unsubscribe@</unsubscribe>
      <post>post@</post>
      <archive>mail-archive</archive>
      <otherArchives>

            One way to eliminate the warnings is to make base.testModule include the not really
            necessary <inherits> lines for c.g.c.collect.testModule, etc. However, adding <inherits>
            lines could make c.g.c.base.testModule transitively inherit from extra modules. If some
            of those modules are ones that it uses but forgets to list in its own <inherits>, we'd

  <groupId>org.apache.maven.its.mng3843</groupId>
  <artifactId>parent-1</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <mailingLists>
    <mailingList>
      <name>parent-mailing-list</name>
    </mailingList>
  </mailingLists>

                   Why? At some point, presumably after
                   https://github.com/google/guava/commit/e06a8cec65815599e510d7f9c1ea9d2a8eaa438a,
                   builds with JDK8 began failing animal-sniffer with the error:

                   Failed to check signatures: Bad class file .../CollectionFuture$ListFuture.class

                   One way of dealing with that would be to disable

          </association>
        </field>
      </fields>
      <comment>We could probably have a specific element for a dev mailing list for things like CI,
        and maybe even a specific element for the user and scm mailing lists. Then leave the more
        lose structure for any other type of mailing list.</comment>
      <codeSegments>
        <codeSegment>
          <version>4.0.0+</version>
          <code>

    </developer>
  </developers>
  <contributors>
    <contributor>
      <name>parent-contributor</name>
    </contributor>
  </contributors>

  <mailingLists>
    <mailingList>
      <name>parent-mailing-list</name>
    </mailingList>
  </mailingLists>

  <prerequisites>
    <maven>2.0</maven>
  </prerequisites>

  <modules>
    <module>child-1</module>
    <module>child-2</module>
  </modules>

            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>
          <version>1.0.0</version>
          <association>