<inspection_tool class="BodyLimit" enabled="true" level="WARNING" enabled_by_default="true" />
      <inspection_tool class="GrazieCommit" enabled="true" level="TYPO" enabled_by_default="true" />
      <inspection_tool class="SubjectBodySeparation" enabled="true" level="ERROR" enabled_by_default="true" />
      <inspection_tool class="SubjectLimit" enabled="true" level="WARNING" enabled_by_default="true" />
    </profile>
  </component>

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

          <description>
            Marks this Mojo as being thread-safe, i.e. the Mojo safely supports concurrent execution during parallel
            builds. Mojos without this annotation will make Maven output a warning when used during a parallel build
            session.
            @since Maven 3.0.
          </description>
          <defaultValue>false</defaultValue>
        </field>
        <field>

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

  <artifactId>coreit</artifactId>
  <version>0.1</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-3839</name>
  <description>
    Test that POM parsing properly coalesces text data.
  </description>

  <properties>
    <!--
    This checks the coalescing of CHARACTERS and CDATA events. Note that inner whitespace must be retained.
    -->

    <inspection_tool class="SystemOutErr" enabled="true" level="WARNING" enabled_by_default="true">
      <scope name="Tests" level="WARNING" enabled="false" />
    </inspection_tool>
    <inspection_tool class="TeardownCallsSuperTeardown" enabled="true" level="WARNING" enabled_by_default="true" />
    <inspection_tool class="TeardownIsPublicVoidNoArg" enabled="true" level="WARNING" enabled_by_default="true" />

    <inspection_tool class="21f28a86-2ba8-3048-9ce1-b6f10d4d4a12" enabled="true" level="WEAK WARNING" enabled_by_default="true" editorAttributes="INFO_ATTRIBUTES" />
    <inspection_tool class="62125fc1-a999-3cf1-9b9b-a30b4375d9bf" enabled="true" level="WARNING" enabled_by_default="true" />
    <inspection_tool class="73cd39e8-e54e-3a38-ad1b-b883fff4b1eb" enabled="true" level="WEAK WARNING" enabled_by_default="true" editorAttributes="INFO_ATTRIBUTES" />

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