static within the build process, but rather to be setup as an aggregation of
  all settings-related information passed into the system.

** Control over downloads

  Find the control point for m2 using maven-wagon. At this point, inject
  a offline status parameter which is used when retrieving the specific Wagon.

  If <<<offline == true>>>:

  * If the wagon is not bound to "file://", then ignore the request and print

        <groupId>org.codehaus.plexus</groupId>
        <artifactId>plexus-utils</artifactId>
        <version>1.0.4</version>
      </dependency>
    </dependencies>
  </dependencyManagement>
  <!-- TODO: point to ref location
    <distributionManagement>
      <site>
        <id>apache.website</id>
        <url>scp://people.apache.org/www/maven.apache.org/wagon/</url>
      </site>
    </distributionManagement>
  -->

        <groupId>org.codehaus.plexus</groupId>
        <artifactId>plexus-utils</artifactId>
        <version>1.0.4</version>
      </dependency>
    </dependencies>
  </dependencyManagement>
  <!-- TODO: point to ref location
    <distributionManagement>
      <site>
        <id>apache.website</id>
        <url>scp://people.apache.org/www/maven.apache.org/wagon/</url>
      </site>
    </distributionManagement>
  -->

 * classloading capability - remote resolution of dependencies - do we want a model for sharing
 * information among plugins, is this more like an extension point - do we need a sort of bus for
 * application data - do we need a dictionary for our applications like Apple does. We could easily
 * hook into this and this is the model we need to follow - how many of our REST services do not map