<!--
      | We may potentially want to export these, but right now I'm not sure that anything Guice specific needs
      | to be made available to plugin authors. If we find people are getting fancy and want to take advantage of
      | Guice specifics we can expose that later. Really some testing needs to be done to see full hiding

      </dependency>
      <!--end-->
    </dependencies>
    <!--start-->
  </dependencyManagement>
  <!--end-->
  <distributionManagement>
    <site>
      <id>apache.website</id>
      <url>scp://people.apache.org/www/maven.apache.org/ref/${project.version}/</url>
    </site>
  </distributionManagement>
  <profiles>
    <profile>
      <id>osgi</id>
      <build>
        <plugins>
          <plugin>

      </dependency>
      <!--end-->
    </dependencies>
    <!--start-->
  </dependencyManagement>
  <!--end-->
  <distributionManagement>
    <site>
      <id>apache.website</id>
      <url>scp://people.apache.org/www/maven.apache.org/ref/${project.version}/</url>
    </site>
  </distributionManagement>
  <profiles>
    <profile>
      <id>osgi</id>
      <build>
        <plugins>
          <plugin>

      </dependency>
      <!--end-->
    </dependencies>
    <!--start-->
  </dependencyManagement>
  <!--end-->
  <distributionManagement>
    <site>
      <id>apache.website</id>
      <url>scp://people.apache.org/www/maven.apache.org/ref/${project.version}/</url>
    </site>
  </distributionManagement>
  <profiles>
    <profile>
      <id>osgi</id>
      <build>
        <plugins>
          <plugin>

   |
   | It works like this: a POM may declare a repository to use in resolving certain artifacts.
   | However, this repository may have problems with heavy traffic at times, so people have mirrored
   | it to several places.
   |
   | That repository definition will have a unique id, so we can create a mirror reference for that

      <w>nondeterministic</w>
      <w>nullable</w>
      <w>overridable</w>
      <w>pseudocode</w>
      <w>substitutor</w>
      <w>subtyping</w>
      <w>supertype</w>
      <w>supertypes</w>
      <w>tuple</w>
      <w>unary</w>
    </words>
  </dictionary>

  <packaging>pom</packaging>
  <name>Multi Chapter Simple Parent Project</name>

  <modules>
    <module>simple-weather</module>
    <module>simple-webapp</module>

    <!-- On purpose at the end, project graph is responsible for ordering -->
    <!-- Build/consumer should not be effected by reverse order -->
    <module>simple-testutils</module>
    <module>utils-parent</module>
  </modules>

  <build>