</array>
          </value>
        </entry>
        <entry key="$PROJECT_DIR$/js/js.translator/testData/lineNumbers">
          <value>
            <array>

 |
 |                 -gs /path/to/global/settings.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation. Where appropriate, the default
 | values (values used when the setting is not specified) are provided.
 |
 |-->
<settings xmlns="http://maven.apache.org/SETTINGS/1.3.0"

    <exportedArtifact>org.slf4j:slf4j-api</exportedArtifact>
    <exportedArtifact>org.fusesource.jansi:jansi</exportedArtifact>

    <!--
      | We must also filter out the old Aether or NoClassDefFoundErrors will surface
     -->
    <exportedArtifact>org.sonatype.aether:aether-api</exportedArtifact>
    <exportedArtifact>org.sonatype.aether:aether-spi</exportedArtifact>

  </repositories>

  <build>
    <defaultGoal>initialize</defaultGoal>
    <directory>out</directory>
    <sourceDirectory>src/main</sourceDirectory>
    <scriptSourceDirectory>src/scripts</scriptSourceDirectory>
    <testSourceDirectory>src/test</testSourceDirectory>
    <outputDirectory>out/main</outputDirectory>
    <testOutputDirectory>out/test</testOutputDirectory>
    <resources>
      <resource>

        <executions>
          <execution>
            <id>Outside ||${project.basedir}||</id>
            <configuration>
              <plugin-all-profiles-out>Outside ||${project.basedir}||</plugin-all-profiles-out>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

  <profiles>
    <profile>
      <id>activeProfile</id>

          <description>The name of the file that must exist to activate the profile.</description>
        </field>
      </fields>
    </class>
    <!--
    This can be put back in when we figure out how to have multiple model versions
    <class>
      <name>ActivationCustom</name>
      <version>4.1.0+</version>

 |
 |                 -gt /path/to/global/toolchains.xml
 |
 | The sections in this sample file are intended to give you a running start at
 | getting the most out of your Maven installation.
 |-->
<toolchains xmlns="http://maven.apache.org/TOOLCHAINS/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

  </dependencies>
  <build>
    <resources>
      <resource>
        <directory>..</directory>
        <includes>
          <include>LICENSE</include> <!-- copied from the parent pom because I couldn't figure out a way to make combine.children="append" work -->
          <include>proguard/*</include>
        </includes>
        <targetPath>META-INF</targetPath>
      </resource>
    </resources>
    <plugins>
      <plugin>

        <reportSets>
          <reportSet>
            <id>Outside ||${project.basedir}||</id>
            <configuration>
              <plugin-all-profiles-out>Outside ||${project.basedir}||</plugin-all-profiles-out>
            </configuration>
          </reportSet>
        </reportSets>
      </plugin>
    </plugins>
  </reporting>

  <profiles>
    <profile>
      <id>activeProfile</id>

  <artifactId>parent</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <!--
  NOTE: This extends the test to check an edge case of URL adjustment which must not error out during inheritance
  if the child misses the artifactId (as to be reported by validation).
  -->
  <url>https://maven.apache.org/</url>