see <a href="../maven-core/artifact-handlers.html">default artifact handlers</a> for a list,</li>
            <li>distinguishing two artifacts
            that belong to the same POM but were built differently.
            For example, {@code jdk14} and {@code jdk15}.</li>
            </ul>
            ]]>
          </description>
          <type>String</type>

            covered by testModule.gwt.xml. Maybe I'll try it someday.

            [*] https://code.google.com/p/google-web-toolkit/wiki/ResourceOracle#When_multiple_PathPrefix_es_have_the_same_path
                https://code.google.com/p/google-web-toolkit/issues/detail?id=7581
            -->
          <execution>
            <id>gwt-test</id>
            <goals>
              <goal>test</goal>

    if match is found, the toolchain instance is made available to other Maven plugins.</p>
    <p>With {@code jdk} toolchain, for example, instead of being stuck with the JDK used to run Maven, all plugins can use
    the same other JDK instance without hardcoding absolute paths into the {@code pom.xml}
    and without configuring every plugin that require path to JDK tools.</p>

                   If we're building with JDK8, then clearly we're sticking to
                   JDK8 APIs. However, I assume (but did not confirm) that we'd
                   have the same issue with our -android builds, which need
                   animal-sniffer so that they can check that we're sticking to
                   JDK6-like APIs.