Implement a skeleton of Mojo Application manifests.

In this first cut, when a local .mojo or .exe target is loaded, we look for a manifest json file nearby and consume it into a catalog maintained by the PackageManagerImpl.

Default manifests are provided for several interesting Mojo apps in Chromium, with pretty names to make the Mash Task Viewer look a little nicer.

Future CL improvements:
- comprehensive testing. currently mojo_shell_apptests is broken due to the EDK change.
- persisting the consumed catalog in a single store (e.g. Preferences) so that we don't need to read a bunch of files every startup. i.e. implement ApplicationCatalogStore.
- block creating the ApplicationInstance on having read the manifest, so the base CapabilityFilter is understood.
- implement base CapabilityFilter application.

R=rockot@chromium.org
http://crbug.com/575858

Review URL: https://codereview.chromium.org/1641043002

Cr-Commit-Position: refs/heads/master@{#372853}

1 files changed, 2 insertions, 2 deletions

diff --git a/mojo/shell/standalone/context.cc b/mojo/shell/standalone/context.cc
index 22e9414..f03cb61 100644
--- a/mojo/shell/standalone/context.cc
+++ b/mojo/shell/standalone/context.cc
@@ -215,8 +215,8 @@ bool Context::Init(const base::FilePath& shell_file_root) {
                            task_runners_->io_runner(),
                            embedder::ScopedPlatformHandle());
 
-  package_manager_ =
-      new PackageManagerImpl(shell_file_root, task_runners_->blocking_pool());
+  package_manager_ = new PackageManagerImpl(
+      shell_file_root, task_runners_->blocking_pool(), nullptr);
   InitContentHandlers(package_manager_, command_line);
 
   RegisterLocalAliases(package_manager_);