Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    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

      <subscribe>subscribe@</subscribe>
      <unsubscribe>unsubscribe@</unsubscribe>
      <post>post@</post>
      <archive>mail-archive</archive>
      <otherArchives>
        <otherArchive>other-archive</otherArchive>
      </otherArchives>
    </mailingList>
  </mailingLists>

  <prerequisites>
    <maven>2.0.1</maven>
  </prerequisites>

  <scm>
    <url>https://project.url/trunk</url>

    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    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

    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    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

    Java package; see https://goo.gl/pRV3Yn for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    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

  <version>0.1</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-3904</name>
  <description>
    Test that properties which refer to build directories which in turn refer to other build directories are
    properly interpolated.
  </description>

  <properties>
    <!-- These are the properties of interest -->
    <dir0>${project.build.outputDirectory}/dir0</dir0>

  <artifactId>test2</artifactId>
  <version>0.1</version>

  <name>Maven Integration Test :: MNG-4000</name>
  <description>
    Test that plugin executions without id are not lost among other plugin executions.
  </description>

  <build>
    <!-- NOTE: This test uses plugin management for the IT plugin. -->
    <pluginManagement>
      <plugins>
        <plugin>

      <subscribe>subscribe@</subscribe>
      <unsubscribe>unsubscribe@</unsubscribe>
      <post>post@</post>
      <archive>mail-archive</archive>
      <otherArchives>
        <otherArchive>other-archive</otherArchive>
      </otherArchives>
    </mailingList>
  </mailingLists>

  <prerequisites>
    <maven>2.0.1</maven>
  </prerequisites>

  <scm>
    <url>https://project.url/trunk</url>

    builds, dependency management, documentation creation, site
    publication, and distribution publication are all controlled from
    the declarative file. Maven can be extended by plugins to utilise a
    number of other development tools for reporting or the build
    process.
  </description>
  <url>http://maven.apache.org/</url>
  <inceptionYear>2001</inceptionYear>
  <properties>
    <classWorldsVersion>1.3</classWorldsVersion>

     */
    public boolean equals(Object other) {
        if (this == other) {
            return true;
        } else if (!(other instanceof ToolchainModel)) {
            return false;
        } else {
            ToolchainModel that = (ToolchainModel) other;
            return java.util.Objects.equals(this.getType(), that.getType())