+ Make sure you have a [GitHub account](https://github.com/signup/free).
+ If you're planning to implement a new feature, it makes sense to discuss your changes
  on the [dev list](https://maven.apache.org/mailing-lists.html) first.
  This way you can make sure you're not wasting your time on something that isn't
  considered to be in Apache Maven's scope.
+ Submit a ticket for your issue, assuming one does not already exist.

     */
    void add(Problem.Severity severity, String message, int line, int column, Exception cause);

    /**
     * The next messages will be bound to this source. When calling this method again, previous messages keep
     * their source, but the next messages will use the new source.
     *
     * @param source a source
     */
    void setSource(String source);

    /**
     *

         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <!-- Shared parent. Doesn't define a lot of things about Apache like general mailing lists, but does
       define the settings common to all projects at Apache -->
  <groupId>org.apache</groupId>
  <artifactId>apache</artifactId>
  <version>1</version>
  <packaging>pom</packaging>

         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <!-- Shared parent. Doesn't define a lot of things about Apache like general mailing lists, but does
       define the settings common to all projects at Apache -->
  <groupId>org.apache</groupId>
  <artifactId>apache</artifactId>
  <version>3</version>
  <packaging>pom</packaging>

    </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>

          </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>

      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but

    }

    @Test
    void testMailingListsAreInheritedButNotAggregated() throws Exception {
        PomTestWrapper pom = buildPom("mailing-lists-inheritance/child-2");
        assertEquals(1, ((List<?>) pom.getValue("mailingLists")).size());
        assertEquals("child-mailing-list", pom.getValue("mailingLists[1]/name"));
    }

    @Test
    void testPluginInheritanceOrder() throws Exception {

  <version>0.1-SNAPSHOT</version>

  <mailingLists>
    <mailingList>
      <name>blah</name>
    </mailingList>
  </mailingLists>

  <build>
      <testSourceDirectory>../sibling/src-test</testSourceDirectory>
      <sourceDirectory>../sibling/src-main</sourceDirectory>
      <resources>
        <resource><directory>blah</directory></resource>
      </resources>
  </build>

  <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>