Make the ChromeBrowserInitializer the only way to start the browser process.

Make the ChromeBrowserInitializer the only way to start the browser process.

Removes the need for talking to the Android application,
which will allow us to slowly move browser specific class
initialization to something browser process specific.

BUG=482445
Committed: https://crrev.com/6c5bbb3ce0d88c89205776a553158c444c393c99
Cr-Commit-Position: refs/heads/master@{#364900}

[Ted C, 2015-12-11 19:59:26]

tedchoc@chromium.org changed reviewers:
+ yfriedman@chromium.org, yusufo@chromium.org

[Ted C, 2015-12-11 19:59:27]

PTAL

[Yusuf, 2015-12-11 21:06:26]

lgtm

[Yaron, 2015-12-11 22:11:08]

lgtm 
nice start!

https://codereview.chromium.org/1521013002/diff/1/chrome/android/java/src/org...
File
chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabsConnection.java
(right):

https://codereview.chromium.org/1521013002/diff/1/chrome/android/java/src/org...
chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabsConnection.java:161:
private static void initializeBrowser(final ChromeApplication app) {
You could get rid of this ChromeApplication dep now (but also ok in follow-up)

[Ted C, 2015-12-12 01:29:10]

https://codereview.chromium.org/1521013002/diff/1/chrome/android/java/src/org...
File
chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabsConnection.java
(right):

https://codereview.chromium.org/1521013002/diff/1/chrome/android/java/src/org...
chrome/android/java/src/org/chromium/chrome/browser/customtabs/CustomTabsConnection.java:161:
private static void initializeBrowser(final ChromeApplication app) {
On 2015/12/11 22:11:08, Yaron wrote:
> You could get rid of this ChromeApplication dep now (but also ok in follow-up)

Certainly can get rid of it from this particular method.  Done.  Will
investigate
at a wider class level later.

[Ted C, 2015-12-12 03:24:10]

The CQ bit was checked by tedchoc@chromium.org

[Ted C, 2015-12-12 03:24:11]

The patchset sent to the CQ was uploaded after l-g-t-m from yusufo@chromium.org,
yfriedman@chromium.org
Link to the patchset: https://codereview.chromium.org/1521013002/#ps20001
(title: "yfriedman@ comment")

[commit-bot: I haz the power, 2015-12-12 03:25:26]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1521013002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1521013002/20001

[commit-bot: I haz the power, 2015-12-12 04:16:39]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-12-12 04:17:34]

Description was changed from

==========
Make the ChromeBrowserInitializer the only way to start the browser process.

Removes the need for talking to the Android application,
which will allow us to slowly move browser specific class
initialization to something browser process specific.

BUG=482445
==========

to

==========
Make the ChromeBrowserInitializer the only way to start the browser process.

Removes the need for talking to the Android application,
which will allow us to slowly move browser specific class
initialization to something browser process specific.

BUG=482445

Committed: https://crrev.com/6c5bbb3ce0d88c89205776a553158c444c393c99
Cr-Commit-Position: refs/heads/master@{#364900}
==========

[commit-bot: I haz the power, 2015-12-12 04:17:35]

Patchset 2 (id:??) landed as
https://crrev.com/6c5bbb3ce0d88c89205776a553158c444c393c99
Cr-Commit-Position: refs/heads/master@{#364900}