Update WebAPKs even if the WebAPK start URL has no Web Manifest part 1/3

chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkMetaData.java

Index: chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkMetaData.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkMetaData.java b/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkMetaData.java
new file mode 100644
index 0000000000000000000000000000000000000000..e3b1ea23e276926889542054d5f4c51166df8be2
--- /dev/null
+++ b/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkMetaData.java
@@ -0,0 +1,24 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+package org.chromium.chrome.browser.webapps;
+
+/**
+ * Meta data from the WebAPK's Android Manifest.
+ */
+public class WebApkMetaData {
+    public int shellApkVersion;

[dominickn, 2016/10/25 07:39:16]

Having all the fields public and no constructor forces this class to be default
constructed and then all the fields are filled in. That's how
FetchedManifestData works. But if you take up my suggestion of having a common
base class between WebappInfo and WebApkInfo, maybe this should be a standard
Java class with private members, a constructor, and getters? It could even have
static Create methods, e.g. createWebappInfoFromWebApk could move its
implementation into here in your follow up. What are your thoughts on the common
base class?

+    public String manifestUrl;
+    public String startUrl;
+    public String scope;
+    public String name;
+    public String shortName;
+    public int displayMode;
+    public int orientation;
+    public long themeColor;
+    public long backgroundColor;
+    public int iconId;
+    public String iconUrl;
+    public String iconMurmur2Hash;
+}