Use a consistent extension id for unofficial builds.
commit528453129efe39f2891cfb2b5a90cea3a0dd645a
authorjamiewalch@chromium.org <jamiewalch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Fri, 7 Jun 2013 08:01:57 +0000 (7 08:01 +0000)
committerjamiewalch@chromium.org <jamiewalch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Fri, 7 Jun 2013 08:01:57 +0000 (7 08:01 +0000)
tree2439be87fc43b64971ae0910c49a8d230bb1eb4d
parent6ac0ea96e93d9ea8029df6bff349f5a9c1a1df61
Use a consistent extension id for unofficial builds.

This will make it easier to test the apps v2 and native messaging
implementations, both of which require a known extension id for the
white-list. Official builds are not affected, since they all end
up with a consistent extension id anyway, via the web-store or the
canary script.

BUG=222855

Review URL: https://chromiumcodereview.appspot.com/16233003

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@204742 0039d316-1c4b-4281-b951-d872f2087c98
remoting/webapp/appsv2.patch
remoting/webapp/build-webapp.py
remoting/webapp/manifest.json