<artifactId>test</artifactId>
  <version>1.0</version>

  <name>MNG-7750</name>
  <description>
    Test build plugin and execution interpolation.
  </description>

  <properties>
    <prop-outside>||${project.basedir}||</prop-outside>
  </properties>

  <build>
    <plugins>
      <plugin>
        <artifactId>plugin-all-profiles</artifactId>
        <executions>
          <execution>

  <parent>
    <groupId>org.my.group</groupId>
    <artifactId>parent</artifactId>
  </parent>
  <artifactId>child</artifactId>
  <packaging>jar</packaging>

  <properties>
    <prop-child>bar</prop-child>
  </properties>
  <dependencies>
    <dependency>
      <groupId>org.slf4j</groupId>
      <artifactId>slf4j-api</artifactId>
    </dependency>
  </dependencies>

  <artifactId>test</artifactId>
  <version>1.0</version>

  <name>MNG-7750</name>
  <description>
    Test reporting plugin and reportSet interpolation.
  </description>

  <properties>
    <prop-outside>||${project.basedir}||</prop-outside>
  </properties>

  <reporting>
    <plugins>
      <plugin>
        <artifactId>plugin-all-profiles</artifactId>
        <reportSets>
          <reportSet>

      <version>5.10.1</version>
      <scope>test</scope>
    </dependency>
  </dependencies>

  <profiles>
    <profile>
      <id>release</id>
      <properties>
        <prop>foo</prop>
      </properties>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>

    for prod and one for tests. However, unlike our other packages, as of this
    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for
    tests, either. This causes it to fail to find AtomicLongMapTest.

    Our workaround is to tell GWT that util.concurrent and all other packages

    POM has a non-empty element and the child POM has an empty element to join.
  </description>

  <properties>
    <prop0>test</prop0>
  </properties>

  <repositories>
    <repository>
      <id>equal-repo-id</id>
      <url>https://maven.apache.org/null</url>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>

    for prod and one for tests. However, unlike our other packages, as of this
    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for
    tests, either. This causes it to fail to find AtomicLongMapTest.

    Our workaround is to tell GWT that util.concurrent and all other packages

    for prod and one for tests. However, unlike our other packages, as of this
    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for
    tests, either. This causes it to fail to find AtomicLongMapTest.

    Our workaround is to tell GWT that util.concurrent and all other packages

    for prod and one for tests. However, unlike our other packages, as of this
    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for
    tests, either. This causes it to fail to find AtomicLongMapTest.

    Our workaround is to tell GWT that util.concurrent and all other packages

    for prod and one for tests. However, unlike our other packages, as of this
    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for
    tests, either. This causes it to fail to find AtomicLongMapTest.

    Our workaround is to tell GWT that util.concurrent and all other packages